Short answer
There is no single best platform. If enquiries are your main goal, your catalogue is small and nobody on staff maintains code, an off-the-shelf platform often fits better. A custom Next.js build pays off when you need custom workflows, CRM or ERP integration, or room to add AI later. ChinGEO only builds custom Next.js sites. The platform itself does not decide rankings.
Short answer: let the business pick the platform
The platform is the last decision, not the first. Start with how buyers reach you (enquiry or online order), how many models you sell and how complex the specs are, how many languages you need, whether leads must flow into a CRM or ERP, whether you plan to add AI, and who will maintain the site. Once those are answered, the choice is usually obvious.
| Option | Best for | Watch out for |
|---|---|---|
| Shopify | Online ordering, tiered pricing, standard products | B2B features depend on your plan; some fixed paths can't be changed |
| WordPress | Enquiry-led sites, frequent content, someone to manage plugins | Multilingual needs plugins; security needs ongoing hardening |
| Custom Next.js | Large catalogues, complex specs, system integration, AI later | Needs a development team; rendering and SEO basics are on you |
A note on scope: ChinGEO only delivers custom Next.js websites. We don't build on Shopify or WordPress. The other two columns are here to help you decide, not to sell you something.
The platform doesn't decide rankings
Search engines and AI assistants care whether a page can be crawled, whether its text is readable, and whether it's relevant. Which platform produced it doesn't matter.
Google's Search Essentials technical requirements come down to three things: Googlebot isn't blocked, the page works (HTTP 200), and it has indexable content. All three options can meet them, and all three can get them wrong.
Custom builds have one specific trap. If the main text only appears after the browser runs JavaScript, some crawlers won't see it. Google's JavaScript SEO basics still recommends server-side rendering or pre-rendering, because it's faster for users and crawlers and not all bots can run JavaScript. For GEO, assume AI crawlers may miss anything rendered only in the browser.
Four problems a custom Next.js build solves
Custom isn't "more advanced". It's useful where off-the-shelf platforms either can't do the job or make it awkward.
- Your own workflows. Quote forms that collect model, quantity and certification needs as separate fields; different product lines for different markets; distributor logins with private documents. On a theme-based platform this usually means stacking plugins. On a custom build it is modelled directly.
- CRM and ERP integration. Leads go straight into your CRM, and specs sync from your ERP or product database, so nobody retypes data. WordPress has a REST API too; the difference is that a custom site's data model is designed around your systems from day one.
- Control over rendering and performance. In Next.js, pages are Server Components by default, so data fetching and HTML rendering happen on the server and less JavaScript reaches the browser (Next.js docs). You also decide which third-party scripts load, how images are handled and where the site is deployed. That is a capability, not a result. Actual speed depends on how the site is built and what gets added later.
- Room for AI. Product Q&A, a selection assistant or enquiry scoring can be added later on the same stack without replatforming. These are custom projects that start with a look at your data and needs. They don't ship with the site.
When an off-the-shelf platform is the better call
If most of these apply, Shopify or WordPress will likely serve you better than a custom build:
- Enquiries are the goal and a form that emails sales is enough
- A few dozen products with simple specs
- No one in-house maintains code, and you don't plan to retain developers
- No CRM, ERP or AI plans for the next year or two
Each platform has its own limits, so read the official docs first. Shopify B2B requires a plan that supports it, features vary by plan, and orders cap at 500 line items (B2B considerations). Fixed paths such as /products and /collections can't be redirected (URL redirects). WordPress doesn't support multilingual sites out of the box and relies on community plugins (multilingual), and themes and plugins need ongoing updates (hardening).
Six questions to decide
| Question | Leans off-the-shelf | Leans custom Next.js |
|---|---|---|
| How do deals start? | Enquiry, or online order for standard items | Multi-step quotes by model and certification |
| Catalogue | Dozens of models, simple specs | Hundreds of models, filterable spec tables |
| Languages and markets | One or two languages | Several markets with different content |
| Systems | Email is enough | Leads into CRM, specs from ERP |
| AI plans | None yet | Product Q&A or enquiry scoring |
| Maintenance | Marketing edits content | A dev team or long-term technical partner |
Pick by situation
| Your situation | Suggestion |
|---|---|
| Enquiry-led, small catalogue, no one to maintain code | Off-the-shelf (WordPress or Shopify) |
| Online ordering with tiered pricing, standard products | Shopify B2B |
| Content-heavy, frequent articles, plugin upkeep covered | WordPress |
| Large catalogue, specs engineers need to verify | Custom Next.js |
| CRM/ERP integration or AI on the roadmap | Custom Next.js |
| Not sure | Run an audit to see where your current site stalls |
We don't take on the first three; a specialist for that platform is the better fit. The last two are what ChinGEO does.
How to read performance scores
Performance is an engineering target. It doesn't guarantee rankings.
- PageSpeed Insights reports mobile and desktop separately, and the two often differ. It also mixes lab data with field data from real users, and the two don't always agree (about PSI).
- Lab results come in four separate categories: Performance, Accessibility, Best Practices and SEO. They aren't one combined score.
- The Performance score moves with test time, device, network and third-party scripts such as ads or A/B tests. Lighthouse says most of that variance comes from changing conditions, not the tool (performance scoring).
- Google says good Core Web Vitals and page experience results don't guarantee top rankings, and the most relevant content still wins (page experience).
ChinGEO treats Core Web Vitals in key overseas regions as an acceptance item, with a target of LCP ≤ 1.8 seconds, checked with PSI and similar tools. It's a delivery target, not a service-level promise, and it says nothing about rankings or AI citations.
Switching platforms without losing rankings
Whether rankings drop depends on how carefully you migrate, not on the new platform. Following Google's site move guide:
- List every old URL, especially pages with traffic or backlinks
- Map each one to a new URL
- Use 301 permanent redirects at launch; Google says these don't cause PageRank loss
- Keep redirects as long as possible, generally at least a year
- Update internal links, the sitemap, canonicals and hreflang
- Watch crawling and indexing in Search Console; a small to medium site usually takes a few weeks for most pages to move
If you're moving onto Shopify, product and collection pages live under the fixed /products and /collections paths, so build the URL map around them.
Common mistakes
- Expecting a new platform to lift rankings. Content and technical basics do that.
- Building a custom site as a front-end showcase. If text needs JavaScript to appear, crawlers may miss it.
- Translating the brochure and calling it a website. Specs an engineer can't check won't be used to make a buying decision.
- Judging by one performance score. Scores vary run to run and between mobile and desktop; look at repeated runs and field data.
- Launching and walking away. Outdated specs and certificates mean buyers and AI assistants get old information.
What ChinGEO provides
We only build custom Next.js sites. Here is what can go into a proposal:
- Custom Next.js only, so the site, AI features and your business systems grow on one stack without replatforming.
- Pages written for three readers: procurement, engineering and compliance, with specs, certifications and documents they can verify (see the lesson why one website has to be written for three readers).
- Server-side rendering or pre-rendering, so crawlers that don't run JavaScript still get the text, plus structured data and hreflang.
- Performance as an engineering target, with Core Web Vitals in the acceptance checklist as described above.
- Your data in your systems: form leads sync to your own CRM, and a visit and lead dashboard is connected after launch.
- Optional AI customer service: AI customer service is a separate service covering knowledge-base answers, multilingual replies and enquiry extraction, with high-intent leads pushed to WeCom or your CRM. It isn't built into every site. A product selection assistant, enquiry scoring or deeper system integration are custom work, scoped separately.
Case in point: for Aikang Medical we built a new English overseas site to Core Web Vitals and multilingual standards.
Where to start
- Run the AI visibility audit to see how your current site does on crawling, readable text, structured data and AI answers.
- Go through the six questions above and decide whether you really need a custom build.
- If you do, see what the export website service delivers and how it's accepted. If you're still comparing site types, start with the lesson on independent sites vs platform stores vs e-brochure sites.
Frequently asked questions
- Does a B2B export website have to be built with Next.js?
- No. If you mostly take enquiries, have a small catalogue and no one to maintain code, an off-the-shelf platform often fits better. Next.js makes sense when you need custom workflows, CRM/ERP integration or AI later.
- Does ChinGEO also build Shopify or WordPress sites?
- No. We only deliver custom Next.js websites, and if an off-the-shelf platform suits you better, we'll say so.
- Will switching platforms cost me my rankings?
- It depends on the migration. Google says 301 redirects don't cause PageRank loss; map every old URL and keep the redirects for at least a year. New URLs can take a few weeks or more to settle in results.
- Does the site come with AI features at launch?
- No. AI customer service is a separate, optional service, and features like product Q&A or enquiry scoring are built on demand after scoping your data and needs.
- Can a high performance score guarantee rankings?
- No. Google says good page experience doesn't guarantee top rankings and relevant content comes first. We use Core Web Vitals as an acceptance target, not a ranking promise.
Further reading
- Service: Overseas website
- Service: Export SEO
- Service: AI customer service
- Glossary: What are Core Web Vitals, and why must an export website pass them?
- Glossary: What is structured data (Schema and JSON-LD), and what should an export site add?
- Glossary: What are AI crawlers, and should you allow GPTBot, ClaudeBot and PerplexityBot?
- Glossary: What is hreflang, and how do you get it right on a multilingual site?
- Lesson: 1.1 Independent site, platform store and "e-brochure" site: what is the difference
- Lesson: 1.2 Why one website has to be written for three readers
- Lesson: 1.2 Case study: how a 3 a.m. enquiry is caught properly
See how AI describes you today
The free AI visibility audit asks ChatGPT, Perplexity and Gemini questions as an overseas buyer would, and checks your website’s technical foundation.