Back to blog

Advanced Technical SEO: Hreflang, JavaScript, Logs and Facets

SEO Course

Advanced Technical SEO: Hreflang, JavaScript, Logs and Facets

By Forsa | SEO Audit and Technical SEO Specialist

Advanced technical SEO for larger sites: hreflang, JavaScript rendering, server logs, pagination, faceted navigation, structured data and ongoing checks.

Updated 11 November 2026 · Part of the SEO guide series

Short answer: Advanced technical SEO deals with the problems that appear once a site is larger or more complex: multiple languages and countries (hreflang), JavaScript-driven pages, thousands of near-duplicate URLs from filters and pagination, and crawling that you need to understand from server logs. The aim is the same as in the basics: let search engines find, render and index the right pages and show the right version to each user. Check Google's current documentation before changing anything large, and test on a limited set of pages first. If the basics in our technical SEO foundations guide are not in place, fix those first.

Hreflang for International and Multilingual Sites

Hreflang annotations tell Google which language or regional version of a page to show to which users. They apply when you have equivalent pages in different languages, or in the same language for different countries, such as US and UK English with different pricing.

Key rules from Google's documentation:

  • Each version must list all versions, including itself. Annotations must be reciprocal: if page A points to page B, page B must point to page A.
  • Use valid language codes (ISO 639-1) and optional region codes (ISO 3166-1 alpha-2), such as en-gb or de.
  • Use x-default for a fallback page, such as a language selector or the main version, for users who match no other version.
  • Point to canonical, indexable URLs that return a 200 status.
  • Implement in the HTML head, in HTTP headers or in the XML sitemap, and pick 1 method to keep it manageable.
<link rel="alternate" hreflang="en-us" href="https://example.com/us/pricing/" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/pricing/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/preise/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/pricing/" />

Common mistakes: missing return links, wrong codes such as en-uk (the correct region code for the United Kingdom is gb), pointing to redirected or noindex URLs and automatic redirects by IP address, which can stop Google from seeing every version. Hreflang is a signal, not a command, and Google can still choose a different version.

JavaScript SEO and Rendering

Google can render JavaScript, but rendering is a separate step that can add delay, and other crawlers, including some AI crawlers, may not render it at all. The safest approach is to deliver the main content and links in the HTML.

ApproachHow it worksGood forWatch for
Static generation (SSG)HTML built ahead of timeBlogs, docs, marketing pagesRebuild needed when content changes
Server-side rendering (SSR)HTML built on the server for each requestFrequently changing pagesServer load and speed
PrerenderingPages rendered ahead of time for crawlers and usersSingle-page apps with mostly static routesKeeping the output in step with the app
Client-side rendering onlyBrowser builds the page from JavaScriptLogged-in app screensContent, links or metadata may be missed or delayed

Google no longer recommends dynamic rendering as a long-term solution, so prefer SSR, SSG or prerendering. Whichever you use:

  • Use real <a href> links for navigation.
  • Put titles, canonicals, meta robots and structured data in the HTML that is delivered, and make sure they match after rendering.
  • Do not block the JavaScript and CSS files that a page needs in robots.txt.
  • Use URL Inspection's rendered view and compare the raw HTML with the rendered DOM.

Server Log Analysis

Server logs record every request, including from Googlebot. Search Console's crawl stats show an overview, while logs show exactly which URLs are crawled, how often and with which status codes. Verify that a visitor claiming to be Googlebot is genuine, because user agents can be faked. Google documents how to verify it with a reverse DNS check.

  1. Collect 30 days of logs and filter for verified Googlebot requests.
  2. Group requests by URL pattern, such as products, categories, filters, parameters and search pages.
  3. Look for patterns that take a large share of crawling but have little value, such as sort and filter URLs.
  4. Look for important pages that are rarely or never crawled.
  5. Check status codes for recurring 5xx or 404 errors, and long redirect chains.

Example: an outdoor equipment store analyzes 30 days of logs (illustrative). About 40% of Googlebot requests go to filter and sort URLs that duplicate category pages, while new product pages are crawled only every few weeks. The store blocks low-value parameter patterns in robots.txt, adds canonical tags where it makes sense, improves internal links to new products and puts them in the sitemap. It re-checks the logs a month later to see whether crawling shifted. Log analysis tools such as Screaming Frog Log File Analyser can help, and a script can do the work for smaller sites.

Crawl Budget

Google says crawl budget matters mainly for very large sites (around 1 million or more pages that change weekly, or 10,000 or more pages that change daily) and sites with many discovered but uncrawled URLs. If that is not your site, keep the structure clean and avoid wasting URLs, but do not spend months on crawl budget.

Pagination

  • Give each paginated page a unique URL that is crawlable with real links.
  • Use a self-referencing canonical on each page. Do not point pages 2, 3 and 4 all to page 1, because that can hide the items on them.
  • Google stopped using rel="next" and rel="prev" as an indexing signal in 2019. They are harmless but not needed.
  • Make sure items on deeper pages are also reachable through category links, internal links or sitemaps.
  • If you use infinite scroll or a "load more" button, provide paginated URLs that crawlers can reach.

Faceted Navigation

Filters such as size, color and price can create vast numbers of near-duplicate URLs. Google has specific guidance on managing faceted navigation:

  1. Decide which filter combinations have real search demand and deserve to be indexed (for example "black running shoes"). Give them clean, stable URLs and unique titles.
  2. For the rest, stop crawling with robots.txt rules for parameter patterns, or use canonical tags to the main category, depending on the case.
  3. Do not rely on noindex for pages that are blocked in robots.txt, because Google cannot see a noindex on a page it cannot crawl.
  4. Use a consistent parameter order and avoid session IDs in URLs.
  5. Link internally to the filter pages that you want crawled, and not to the others.

Structured Data at Scale

For large sites, generate markup from templates and data fields, not by hand. Validate each template, monitor Search Console enhancement reports and update the markup when fields change. See structured data and schema for AI and search visibility and FAQ schema and structured answer markup. Remember that Google no longer shows FAQ or HowTo rich results for most sites.

Entities and Brand Signals

Consistent names, Organization markup with sameAs links, clear About and author pages and accurate profiles help search engines connect your pages to the right entity. See entity clarity.

Ongoing Technical Maintenance

  • Weekly: Search Console indexing and Core Web Vitals reports for new errors.
  • Monthly: a crawl of the site for broken links, redirect chains, duplicate titles and canonical conflicts. A free SEO audit is a quick check for single pages.
  • Quarterly: hreflang, structured data and robots.txt review, and a check of AI crawler access with the AI crawler access check.
  • After releases and migrations: compare before and after crawls, redirects and indexing.

Common Mistakes

  • Hreflang without return links, or pointing to redirected URLs.
  • Client-side rendering for important content and links.
  • Blocking JavaScript or CSS files needed to render the page.
  • Canonicalizing all paginated pages to page 1.
  • Letting filters create thousands of indexable URLs.
  • Using noindex and robots.txt blocks on the same URL.
  • Making big changes without testing on a small set of pages.

Action Checklist

  1. Confirm that the basics are in place.
  2. Test a few key templates with URL Inspection, comparing raw and rendered HTML.
  3. Audit hreflang for reciprocity, codes and canonical targets, if you have several languages.
  4. Review crawl stats and, if the site is large, server logs.
  5. Decide which filter pages deserve indexing.
  6. Document each change and re-check after a few weeks.

Related Guides

FAQs

Do I Need Hreflang?

Only if you have equivalent pages for different languages or regions. A site in 1 language for 1 market does not need it.

Is JavaScript Bad for SEO?

No, but it adds risk. Google can render it, while other crawlers may not, so deliver important content and links in the HTML through SSR, SSG or prerendering.

Do I Need Server Log Analysis?

It is most useful for large sites and for diagnosing crawling problems. Small sites can usually rely on Search Console.

Should I Noindex Paginated Pages?

Generally no. Let paginated pages be crawlable with self-referencing canonicals, so that items listed on them can be discovered.

How Do I Handle Faceted Navigation?

Index only filter combinations with real search demand, keep the rest from being crawled or canonicalize them, and keep URLs consistent. Test the changes on a limited section first.