It is 2026, and two weeks after a website redesign goes live, Google can reach product detail pages while Baidu only returns the homepage for a brand search—are the internal page links all hidden inside buttons?
Opening conclusion: don't rush to change the framework; first check whether the three sources are consistent
A common situation in 2026 is that Google has crawl and render queues for JavaScript rendering, while Baidu relies more on body content and internal links that can be read directly in the source HTML. With the same client-side-rendered SPA, Google may delay indexing some internal pages, while Baidu is more likely to index only the homepage. To judge whether front-end SEO is acceptable, first check whether the source HTML, the rendered DOM, and the crawl results in the webmaster platform are consistent—not just whether the page looks normal in a browser. If the three sources are inconsistent, first add readable body content in the source and followable internal links, then discuss prerendering or SSR.
Front-end SEO here does not mean stuffing keywords into front-end code. It means enabling crawlers, within a limited crawl budget, to do three things: discover URLs, read body content, and understand link relationships between pages, while meeting an acceptable baseline for mobile experience. In 2026, when building corporate websites, content sites, product detail pages, or campaign aggregation pages, if the front end is delivered only against browser experience, indexing differences often show up one to three weeks after launch (experience range).
- Discoverable: whether internal links are real a-tag hrefs rather than click events only; whether list pages have pagination or static entry points.
- Readable: whether above-the-fold body content, titles, and breadcrumbs appear in the source or in stable rendered results.
- Assessable: whether canonical, robots, sitemap, and structured data are consistent with the page's actual content.
Why the same set of pages performs differently in the two search engines
The difference is mainly in crawling and rendering, not page visuals. Google places JS pages into a rendering queue, while Baidu looks more at body content and internal links that can be read directly in the source; this does not mean Baidu does not execute JS at all, but that execution depth, frequency, and crawl budget differ. When there are many internal pages and updates are frequent, sites that rely only on CSR often have a higher proportion of only-homepage indexing in Baidu—this is a typical range, not a certainty for every site.
Also rule out false diagnoses: robots blocking by mistake, incorrect canonical, an outdated sitemap, abnormal server responses to Baidu's UA, or wrong status codes on internal pages. These are not front-end framework issues, but they look very similar. Check crawl diagnostics in the webmaster platform first, then compare the source and rendered DOM; this can avoid detours such as changing the framework unnecessarily.
A practical verification framework: three-source consistency plus four-layer troubleshooting
Breaking front-end SEO into “three-source consistency and four-layer troubleshooting” is because the difference between Google and Baidu is mainly in crawling and rendering, not page visuals. First confirm whether the three sources see the same page, then locate the problem layer by layer; this reduces front-end and operations waiting on each other. The three sources are source HTML, rendered DOM, and crawl results in the webmaster platform; the four layers are routing and status, content and internal links, structured data, and performance and mobile adaptation. Every step should leave a verifiable record, not just a verbal claim that it has been handled.
- Routing and status: confirm whether detail pages, list pagination, and filter pages have stable URLs; whether parameterized pages are accidentally affected by robots or canonical. For acceptance, check whether URLs in the sitemap return 200 and the correct title in the source or crawl results.
- Content and internal links: whether above-the-fold body content, category entry points, and previous/next links are crawlable; do not use div plus click instead of a href. For acceptance, check whether crawl results can follow internal links to second- and third-level pages.
- Structured data: whether markup for products, articles, breadcrumbs, and so on matches visible content; for JSON-LD inserted later by the front end, verify after the DOM is stable. For acceptance, check whether platform testing tools can recognize it without conflicts.
- Performance and mobile adaptation: whether mobile above-the-fold content is pushed back by large images or scripts; set thresholds for LCP, CLS, and other metrics according to experience ranges, and do not test only locally. For acceptance, check whether the body content is still readable on target devices under weak network conditions.
This verification is suitable for running once before QA handoff and once after launch. Before QA handoff, focus on source readability and whether internal links can be followed; after launch, focus on whether webmaster platform crawl results and the rendered DOM are consistent. According to common project delivery practice, run the three-source check before QA handoff, then decide whether to add prerendering; this can reduce rework when Baidu cannot read internal pages only after launch. If the three sources are inconsistent, fix entry points and body content first, then discuss keyword layout.
Solution comparison: applicable boundaries and experience-based costs of SSR, prerendering, and pure CSR
Common front-end SEO solutions are not better when heavier; they should be allocated by page type. In 2026 project delivery, for pages that rely on search for organic traffic—such as corporate website homepages, content detail pages, and product detail pages—server-side rendering or build-time generation is usually preferred. For admin panels, post-login pages, and highly interactive tool pages, pure client-side rendering is generally sufficient, and there is no need to adopt a heavy solution for indexing. The criterion is: does the page need to be found by search when the user is not logged in and not interacting?
- SSR or SSG: the source directly contains body content and internal links, so both Google and Baidu can read it easily; the cost is that the front end must handle isomorphic rendering, caching, and deployment, with common modification effort of about 5–15 person-days depending on page scale (experience range).
- Prerendering: suitable for corporate websites, campaign aggregation pages, and help centers with a controllable number of pages; static HTML is generated at build time, with smaller changes, commonly 2–5 person-days (experience range), but pages with many dynamic parameters need a whitelist.
- Pure CSR plus static entry points: suitable for admin panels and low-frequency internal pages; requires adding a sitemap, static navigation, and above-the-fold summaries, commonly 1–3 person-days (experience range), but Baidu's stability in indexing internal pages is usually weaker than the first two.
When comparing, do not look only at development cost; also consider content update frequency and operations capacity. SSR is not a one-time fix: cache invalidation and API timeouts can both affect crawling. Prerendering is vulnerable to page-count explosion and missed whitelist entries; pure CSR is vulnerable to internal links that rely entirely on JS events. Writing “who maintains the URL list, who checks the webmaster platform, and who handles crawl anomalies” into the delivery checklist is more effective than debating frameworks.
Delivery experience and applicable boundaries
A common constraint in projects is this: the budget only covers a pure front-end SPA, the APIs and assets are not finalized until one week before launch, and the team launches with CSR first. As a result, Google gradually crawls some internal pages, while Baidu indexes only the homepage for a long time. When reworking to add prerendering, static internal links, and a sitemap, front-end and operations each spend about 3–8 extra person-days (experience range), and the release is delayed. This cost is usually not because the code is wrong, but because the launch gate does not include “crawlable body content and internal links.”
Before delivery, verify three things first: whether the core above-the-fold text can be read in the source; whether there are followable a tags between lists and detail pages; whether robots, canonical, and sitemap conflict with one another. Common pitfalls include: loading important content only after a click, using hash routing for detail pages that need indexing, hiding body content in a collapsed layer on mobile that is closed by default, and pointing canonical to the wrong page. What counts as acceptable: without executing complex interactions, crawl results can see the page topic and links to the next layer.
Situations suitable for prioritizing front-end SEO verification: corporate websites, content sites, product detail pages, help centers, campaign aggregation pages, and other pages that rely on organic search traffic; the team can obtain webmaster platform permissions and is willing to watch crawl and indexing changes for two to four weeks after launch (experience range). When covering both Google and Baidu, first ensure source readability and the mobile baseline, then add structured data and internal links according to platform feedback.
Also state clearly when a heavy solution is unnecessary: post-login admin panels, internal tools, highly interactive editors, and single pages deployed only in private domains or as ad landing pages that do not expect search indexing should prioritize experience and delivery cycle, and do not need SSR for indexing. Boundary statement: if a page does not need to be discovered through search by users who are not logged in, front-end SEO investment should be narrowed according to brand display and share-card needs, rather than copying the content-site approach.
- Counterexample: list cards only have an onclick jump and no href; crawlers cannot follow the list to discover detail pages.
- Counterexample: detail page body content is mounted only after the API returns, and the source contains only a loading image; Baidu can easily fail to read it.
- Acceptance line: the source or stable rendered result contains the title, body summary, breadcrumbs, and at least one followable internal link.
FAQ
Google can execute JS, so does the front end no longer need server-side rendering?
Not necessarily. Google renders JS, but crawling and rendering have queues and delays. When there are many internal pages and updates are frequent, relying only on CSR can leave some URLs unindexed for a long time; key pages should still have readable source HTML.
Baidu only indexes the homepage—should we change the front-end routing first or check the webmaster platform first?
Check crawl diagnostics, robots, and sitemap in the webmaster platform first, then decide whether to change the front end. If crawl results show that internal pages return an empty shell or error status, prioritize adding source body content and internal links rather than changing the framework first.
Is there a big difference between prerendering and SSR for front-end SEO?
For crawlers, both can provide readable HTML; the difference is in maintenance. Prerendering suits sites with a controllable number of pages, while SSR suits pages with frequent content updates and many parameters, and costs more.
If internal links use div plus click events, can search engines follow them?
Usually they cannot follow them reliably. Crawlers rely more on a-tag hrefs to discover new URLs; with div plus script jumps, internal pages may lack entry points for a long time, so list pages should keep real links.
How long after launch is it reasonable to watch indexing changes?
Based on 2026 project experience, a common observation window is two to four weeks. Look at crawl frequency and indexed volume first, then rankings; during this period, do not frequently change canonical and routing structure, to avoid creating fluctuations yourself.
If this set of pages must face both Google and Baidu, first make readable source body content, followable internal links, and the mobile baseline into launch checklist items, then iterate according to webmaster platform feedback; for campaign pages that only serve brand display and whose internal pages do not expect search traffic, there is no need to adopt heavy SSR for indexing.
-
If an API occasionally returns null and a product card prints “null,” should the fallback live in data fetching or rendering?
Date: Nov 22, 2026 Read: 8
-
In admin lists, when a product name gets long, the Edit/Unpublish button is pushed off screen—should the ellipsis go on the title or the outer container?
Date: Nov 21, 2026 Read: 8
-
In 2026, AI-generated pages work fine on the normal path, but what happens when the network drops, users click repeatedly, or they hit back? Are these edge states the frontend team's job?
Date: Nov 20, 2026 Read: 18
-
In 2026, product says only “make it a bit smoother” before a project starts—then brings up experience before launch. Who should kick off the experience target sheet?
Date: Nov 19, 2026 Read: 12
-
A coupon pop-up is still open in WeChat, but pressing Back on the phone exits the whole campaign page—who should own the Back button?
Date: Nov 18, 2026 Read: 20




