Last time I explained why I switched from The7 to Astra. A few business owners followed up with a practical question: “Okay, the theme is sorted. But how long does it actually take to build a WordPress + Astra site from scratch to going live?”
There’s a common misconception about WordPress site building: install a theme, drag a few modules, fill in some text — half a day, done. I thought the same thing when I started.
The reality of building a foreign trade independent site from start to finish: it took me about 6 days on and off, and I hit 7 pitfalls along the way. One of them cost me half a day of rework.
This isn’t a tutorial. There are plenty of those online — most are just “click here, click there” step lists. What I want to write is what I actually did: each step, how long it took, what went wrong, and why.
If you’re planning to build your own site, or you’re paying someone to build one and want to know what they’re actually doing, this record might save you some detours.
Step 1: Buy Domain and Server (Half a Day)
Domain
Your domain is your site’s street address. A few principles for choosing one:
Go with .com first. Foreign trade sites target overseas customers, and .com has the highest international recognition. A .cn domain works, but overseas customers sometimes see .cn and think “local Chinese business” rather than “international company.” I use ddjianzhan.cn myself because my primary market is domestic; if your customers are abroad, prioritize .com.
Keep it short and memorable. If your company name is long, use an abbreviation plus an industry word — something like “xx-hardware.com.”
Check the domain’s history. Some domains were previously used and may have been penalized by Google. Before registering, check with the Wayback Machine, or just pick a fresh domain with no history.
Server
The server is where your site “lives.” Foreign trade sites have three server requirements:
- Location: Put the server where your target customers are. Clients in Europe or the US? Choose a US or Hong Kong server. Clients in Southeast Asia? Choose Singapore.
- Specs: WordPress itself isn’t resource-heavy, but the Elementor editor is memory-intensive.
- Bandwidth: Foreign trade sites have lots of images. Low bandwidth means slow image loading.
Pitfall #1: Server specs too low.
The first time around, I chose a 1-core, 1GB entry-level server (the kind that costs about $15/year). WordPress had barely been installed — Elementor wasn’t even on yet — and it was already sluggish. After installing Elementor, the editor went completely white-screen: the page opened blank, nothing displayed.
The reason is simple: every time you save in Elementor, it renders the entire page’s HTML server-side. 1GB of RAM can’t handle that. After upgrading to 4-core, 4GB, the problem disappeared.
If budget is tight, start with a minimum of 2-core, 2GB. But my recommendation is to go straight to 4-core, 4GB. The extra cost over a year is negligible, and you won’t spend the entire build process pulling your hair out over lag.
Step 2: Install WordPress and Configure (1–2 Hours)
Installation Method
I use aaPanel (BaoTa Panel). It’s the most widely used server management panel — once installed on your server, you can handle everything through a web interface: install Nginx, PHP, MySQL, WordPress — no command line needed.
If you’re technically inclined, you can install everything manually via command line. But honestly, the time aaPanel saves you is worth the small cost.
Initial Configuration
After WordPress is installed, a few settings must be changed before anything else:
Set PHP version to 8.3. WordPress 6.x fully supports PHP 8.3, which is over 15% faster than PHP 7.4. Some older plugins may not be compatible — check after installing each one.
Change PHP memory limit to 512M. The default is 128M. Elementor’s editor needs at least 256M to avoid white-screening. I set it to 512M for plenty of headroom.
Set the timezone to your target market. If your clients are in Germany, set the European timezone. This affects post publication times and backend log timestamps.
Pitfall #2: PHP memory limit doesn’t match server memory.
This one connects directly to the first pitfall. I changed the PHP memory limit to 512M on a 1GB server — but the server only had 1GB total. PHP takes 512M, leaving 512M to run Nginx + MySQL + the OS. Direct OOM (out of memory). Server reboots.
The lesson: server specs and PHP settings must match. A 1GB server can’t run Elementor — start at 2GB minimum. A 4GB server with PHP memory set to 512M works perfectly.
First Batch of Must-Have Plugins
A fresh WordPress install is bare — no functionality at all. I install these three “infrastructure” plugins first:
- WP Mail SMTP: Configures email sending. Without it, your inquiry forms can’t send emails.
- Wordfence Security: Security protection. WordPress gets hacked more often than you’d think.
- WPForms Lite: Contact form so customers can submit inquiries through your site.
These three are non-negotiable, regardless of what theme or editor you install later.
Step 3: Install Astra + Elementor + Core Plugins (1 Hour)
Astra Theme Installation
WordPress admin → Appearance → Themes → Add New → search “Astra” → Install → Activate. The free version is sufficient.
Then install the Starter Templates plugin that comes with Astra. It provides dozens of pre-built website templates you can import and modify. For anyone who doesn’t want to build pages from scratch, this saves an enormous amount of time.
Elementor Installation
Elementor is a page builder. Once installed, you can drag and drop to build pages visually — a component library on the left (headings, images, buttons, forms), a canvas on the right where you arrange and combine them.
The free version handles basic pages. But if you need product catalogs, image carousels, pricing tables, and other advanced widgets, you’ll need Elementor Pro. Foreign trade product showcase pages almost always need these, so I use the Pro version.
SEO and Performance Plugins
This is where I separate from the average site builder. Most people install their theme and editor and start building pages immediately. I install SEO and performance plugins at this stage:
- SureRank: All-in-one SEO toolkit. Manages TDK (Title/Description/Keywords), auto-generates Sitemaps, produces Schema structured data, integrates with Google Search Console. I chose it not because it’s the most popular (Yoast SEO and RankMath have more users) but because its Schema detection and repair is the most granular — it tells you exactly which page, which field is incomplete, down to the individual markup.
- WP Rocket: Caching plugin. Handles page caching, GZIP compression, CSS/JS minification, database optimization, lazy loading — a one-stop solution for most speed issues. Paid plugin, but worth every penny.
- Perfmatters: Script manager. After installing a bunch of WordPress plugins, each one injects its own CSS and JS files into every page. Perfmatters lets you disable unnecessary scripts on a per-page basis — the key tool for controlling “file count.”
Pitfall #3: Too many plugins.
When I first started, I wanted to install every plugin that looked useful — analytics, social sharing, three SEO tools (Yoast + RankMath + SureRank), two form plugins (Contact Form 7 + WPForms), two speed plugins (WP Rocket + Autoptimize).
The result: after installing 20+ plugins, PageSpeed dropped to 60. Each plugin was injecting its own CSS and JS files into every page — the homepage alone loaded 89 CSS/JS files.
After trimming down to 9 plugins, speed returned to normal. The principle: if one plugin can do the job, don’t use two. If you don’t need it, don’t install it.
Step 4: Build Pages (2–3 Days)
This is the most time-consuming part of the entire build.
Page Structure Planning
Before building anything, I sketched out a page structure:
A B2B foreign trade site doesn’t need many pages, but every page must serve a purpose. My principle: if a page doesn’t help the customer make a decision, don’t build it.
Homepage Build
The homepage is the first page customers see, and it’s the hardest to build. Using Elementor, I built a homepage with these sections:
- Hero section: One sentence explaining who you are, what you do, and what outcome customers get
- Service showcase: Three package tiers with a one-line differentiator for each
- Advantages section: Why choose you (technical capability, AI GEO expertise, speed optimization experience)
- Process timeline: From build to launch
- FAQ section: The 5–6 questions customers ask most
- Footer CTA: Contact entry point
Pitfall #4: Over-designing with Elementor.
First-time Elementor users (including past me) tend to make the same mistake: pile everything onto the homepage. Animation effects, scroll parallax, background videos, multi-layered cards — it looks impressive, but every effect loads additional JS files.
My first homepage had 15 animation effects. Mobile load time: 4.2 seconds. After cutting to 3 essential animations (hover effects + button micro-interactions), mobile load dropped to 2.1 seconds.
The principle: for every visual effect, ask yourself — is it helping the customer understand the content, or is it satisfying my design urge?
Other Pages
Product pages and the About page are relatively straightforward, but a few things are worth noting:
Product pages: don’t just show images and specs. A good product page should answer three questions in the customer’s mind — What can this thing do? How’s the quality? How do I contact you? Images and specs only answer the first one. Add application scenarios, technical parameter tables, and common customer questions — the information doubles, and so does the time customers spend on the page.
About page: don’t copy your company profile. Most About pages are just web versions of a company brochure — founding year, headcount, factory area. But customers reading your About page want to confirm one thing: “Is this company reliable?” Team photos, factory floor photos, certifications — these are far more useful than “Founded in XXXX.”
Step 5: Fill In Content (1–2 Days)
Content is the most underestimated part of the process. Many people think “content is just moving text around.” It isn’t.
How to Write Product Descriptions
Pitfall #5: Copying product descriptions directly from Alibaba.
This is what I did at first — copied product information from our Alibaba International store straight to the independent site. Easy, but two problems:
First, Google flags it as duplicate content. Alibaba’s product pages are already in Google’s index. You put the same text on your independent site, and Google considers it “copied content,” lowering your indexing priority.
Second, Alibaba’s descriptions are optimized for the platform, not for your independent site. Platform descriptions have character limits and format requirements. Your independent site has none of those constraints. You can write longer, more detailed, more persuasive product descriptions.
The right approach: rewrite everything. Target the independent site specifically. Add product application scenarios, technical spec tables, and common customer questions. These might not fit on Alibaba, but on your independent site they become a content advantage.
llms.txt
This file is for AI crawlers. Placed in the site’s root directory, it tells ChatGPT, Perplexity, and other AI tools: what my site is, what it does, what key pages exist.
It’s not complicated — just a plain text file. But most web development companies don’t know it exists, because they use SaaS website builders where you can’t place custom files in the root directory. WordPress can. This is one of the concrete examples I mentioned in my previous article about “WordPress doing things AI website builders can’t.”
Step 6: SEO and Structured Data Configuration (Half a Day)
TDK
Every page needs its own Title, Description, and Keywords. SureRank lets you set these per page.
The principle: Title under 60 characters, Description under 160 characters. Anything longer gets truncated by Google in search results, which hurts click-through rate.
Google Search Console
Register with Google Search Console, verify domain ownership, and submit your Sitemap.
This step is critical: it tells Google your site exists and you’ve proactively submitted a sitemap for Google to crawl. A new site without GSC submission might wait weeks or even months for Google to discover it.
Schema Structured Data
Pitfall #6: SureRank found 20+ Schema errors.
After installing SureRank, I ran a full-site Schema check. Results: 20+ incomplete or incorrect markup — some pages were missing Organization markup, some product pages were missing price range, the FAQ page’s Question/Answer structured data format was wrong.
Customers can’t see these issues (Schema lives in the code), but Google and AI can. Incomplete Schema is like handing Google a business card with missing information — it knows who you are, but isn’t sure what you do.
I spent an afternoon fixing each one. After the fixes, Google Search Console started showing “rich results” data — search results now displayed FAQ answers and company information in addition to the title and description. This directly improved search result click-through rates.
Step 7: Speed Optimization (1 Day)
After installing Astra + Elementor + a pile of plugins, don’t rush to go live. Run PageSpeed Insights first and check your score.
My site at this stage: mobile score of 72. Not terrible, but the target for foreign trade sites is 90+ — because Google’s Core Web Vitals is a ranking factor, and low scores directly hurt your rankings.
Here’s what I did for speed optimization:
WP Rocket cache configuration. Enable page caching, GZIP compression, CSS/JS minification. These three are the basics — they’ll take you from 72 to about 80.
Enable OPcache. OPcache is PHP’s built-in bytecode cache. PHP compiles scripts on every execution — OPcache stores the compiled result in memory, so the next time it’s used directly, skipping redundant compilation. Toggle it on in aaPanel’s PHP settings, no extra installation needed. After enabling, PHP execution speed increases by about 30%, and backend operations feel noticeably snappier.
Redis object cache. WordPress queries the database on every page load — frequent queries slow things down. Redis caches database query results in memory. The second time the same content is accessed, it reads directly from Redis instead of hitting the database. Setup: install Redis on the server, install the Redis Object Cache plugin in WordPress, connect with one click. After enabling, database queries per page load drop from about 120 to around 20, and page generation time is cut in half. Only recommended for servers with 2GB+ RAM — on a 1GB server, Redis will eat up too much memory.
Convert images to WebP. Convert all JPG/PNG images to WebP format — same visual quality, 30–50% smaller file size.
CSS/JS cleanup. Use Perfmatters to disable unnecessary scripts on a per-page basis. The “89 CSS/JS files” mentioned earlier? Trimmed to 23. This is the key step from 80 to 90.
Localize Google Fonts. By default, fonts load from Google’s CDN, which can be slow in some regions. Download font files to your own server and load them locally.
Pitfall #7: Over-optimization backfires.
In pursuit of a higher score, I lazy-loaded the Critical CSS (the essential styling needed for above-the-fold content). The result: when the homepage opened, the styling “flashed” — it first showed unstyled HTML, then loaded the CSS. This is technically called FOUC (Flash of Unstyled Content), and the user experience is terrible.
I switched Critical CSS back to inline loading — the homepage now has styling immediately on open. The score dropped from 91 to 89, losing 2 points, but the user experience is far better.
The goal of speed optimization isn’t chasing a perfect score — it’s making the site feel “fast” to the user. The difference between 89 and 91 is imperceptible to users, but FOUC is immediately visible.
Step 8: Testing and Launch (Half a Day)
Pre-Launch Checklist
Before going live, I ran through this checklist:
- Mobile view renders correctly (not just checking on desktop)
- All forms can submit and send emails successfully
- WhatsApp button works on mobile
- SSL certificate is active (https://, not http://)
- 404 page has content (not a default blank page)
- All internal links work
- Google Search Console Sitemap submitted
- llms.txt uploaded to root directory
- Schema verified through Google Rich Results Test
Launch
Point the domain to the server IP, SSL certificate activates, and the site is officially accessible to the public.
The moment of launch was unceremonious. The first thing I did was open the site on my phone over a 4G connection — if it loads within 3 seconds on 4G, the speed passes.
Retrospective: Where the 6 Days Actually Went
| Task | Time | Percentage |
| Domain + Server | Half a day | 8% |
| WordPress install + config | 1–2 hours | 4% |
| Astra + plugin installation | 1 hour | 3% |
| Page building | 2–3 days | 45% |
| Content writing | 1–2 days | 25% |
| SEO + Schema configuration | Half a day | 8% |
| Speed optimization | 1 day | 12% |
| Testing + launch | Half a day | 5% |
Looking at this table, you’ll notice: installing the system and plugins took only 1 day, but building pages and writing content took 3–5 days. About 80% of the time goes to “visible” work (pages and content), and 20% goes to “invisible” work (configuration and optimization).
But what determines whether your site gets indexed by Google, whether it gets recommended by AI — that’s precisely the 20% you can’t see: Schema, llms.txt, speed optimization, structured data.
This is why many “3-day launch” sites from web development companies produce no results — 3 days is enough for the 80% that’s visible, but the invisible 20% gets skipped entirely.
What This Record Means for You
If you’re planning to build your own site, this gives you a reference: from zero to live takes about 6 days, and you’ll hit pitfalls along the way. Hitting pitfalls isn’t scary — not knowing where they are is.
If you’re paying someone to build your site, this record helps you judge whether they’re doing it right: ask what plugins they installed, whether they configured Schema, whether they ran PageSpeed, whether they uploaded llms.txt. If the answer to all of these is no, they only did 80% of the work — the 80% you can see.
The previous article was about theme selection. This one is about the build process. Next, I’ll cover another often-overlooked area — server optimization. My 4-core, 4GB server was eating 4.8GB of memory running WordPress. After spending a day troubleshooting, I got it down to 300MB. How? Find out in the next article.
If you run into specific issues during your own build process, check out the services page — different packages correspond to different depths of technical configuration. Pick based on the results you need.
