Reference
Technical SEO FAQ
Direct, source-backed answers to the technical SEO questions that come up in real work — no fluff. Every answer is written and reviewed by Abhinav Krishna, and cites primary sources.
Core Web Vitals, Performance & HTTP
- How can third-party scripts affect SEO and performance? Third-party scripts can consume CPU, network bandwidth and main-thread time.
- How do Core Web Vitals influence Technical SEO strategy? Core Web Vitals measure real-world aspects of page experience:
- How do you distinguish lab data from real-user performance data? Lab data Generated in a controlled testing environment.
- How do you prioritize performance improvements against other SEO work? Use business and technical impact.
- How does image optimization affect crawling, rendering and user experience? Images affect:
- How should server performance be considered in Technical SEO? Server performance affects:
- How would you diagnose poor LCP? Start by determining what the LCP element is.
- How would you investigate a sudden deterioration in Core Web Vitals? Establish when the change began.
- How would you troubleshoot CLS? Identify which elements shift and why.
- What typically causes poor INP? INP measures responsiveness to user interactions.
Crawling, Crawl Budget & URL Management
- Can blocking a URL in robots.txt solve an indexation problem? Not reliably.
- How do you analyze Googlebot crawl behavior beyond Search Console? Use server logs.
- How do you decide which URL patterns should be crawlable? Create a URL governance matrix.
- How do you determine whether a website actually has a crawl-budget problem? Do not infer a crawl-budget problem from URL count alone.
- How do you differentiate crawl demand from crawl capacity? Google describes crawl budget using two major concepts:
- How do you identify URLs that unnecessarily consume crawler resources? Classify URLs by type and compare crawl activity against SEO value.
- How would you handle millions of faceted-navigation URLs? First determine which facet combinations have genuine search value.
- How would you optimize crawling on a website with millions of URLs? Start with URL governance, not with robots.txt.
- What patterns in server logs indicate inefficient crawling? Common patterns include:
- When would you use robots.txt versus noindex? Use robots.txt primarily for crawl control.
Enterprise Technical SEO, Migrations, Measurement & Leadership
- How do you build technical SEO monitoring for a large website? Automate monitoring of:
- How do you combine Search Console, logs, crawlers and analytics? Each system answers different questions.
- How do you communicate Technical SEO problems to executives? Translate technical problems into business consequences.
- How do you diagnose a sudden organic traffic drop from a technical SEO perspective? Do not immediately assume an algorithm update.
- How do you perform an SEO-safe domain migration? Plan the migration as a URL mapping problem.
- How do you prove that a Technical SEO implementation caused an improvement? Use controlled measurement wherever possible.
- How do you use Google Search Console as a technical SEO diagnostic system? Treat Search Console as one layer of evidence.
- How do you validate a migration before launch? Use a staging or controlled test environment.
- How would you manage Technical SEO during a major redesign? Start before development.
- If you had access to the entire website, server logs, Search Console, analytics and development team, what would your first Technical SEO investigation be? I would not immediately run a crawler and start fixing warnings.
Indexing, Canonicalization & Duplicate Content
- How do you determine why an important page isn't indexed? Use a layered diagnosis:
- How do you investigate "Crawled - currently not indexed"? Treat the status as a diagnostic clue, not a diagnosis.
- How do you investigate "Discovered - currently not indexed"? Start with discovery and crawl efficiency.
- How do you validate whether an indexation fix actually worked? Define validation before implementation.
- How would you identify index bloat? Do not define index bloat simply as "too many indexed pages."
- How would you manage indexation on a large e-commerce website? Create an indexation policy by URL class.
- What happens when canonical and noindex signals conflict? Conflicting signals make the intended outcome less clear.
- What is the difference between crawling, rendering, indexing, ranking and serving? Crawling Google discovers and fetches URLs.
- What signals influence Google's canonical selection? Google may use several signals, including:
- When should a page be canonicalized instead of noindexed? Use canonicalization when multiple URLs represent essentially the same content and you want one representative URL.
International SEO, Structured Data & Advanced Technical Signals
- Can JavaScript generate structured data? Yes.
- How do you approach JavaScript-generated metadata? Important metadata includes:
- How do you handle pagination on large sites? Make pagination discoverable through crawlable links.
- How does hreflang work? hreflang tells Google about localized versions of a page.
- How does structured data fit into Technical SEO? Structured data provides explicit information about page content and entities.
- How should infinite scroll be implemented for SEO? Provide crawlable paginated URLs in addition to the interactive infinite-scroll experience.
- How should you structure international websites? Common architectures include:
- How would you audit structured data at scale? Extract:
- What are common hreflang implementation failures? Common issues include:
- What is the difference between structured data eligibility and ranking? Structured data can make a page eligible for certain search features if Google's requirements are met.
JavaScript SEO & Rendering
- How can JavaScript affect canonical tags? JavaScript can create or modify canonical tags.
- How can JavaScript affect internal linking? A crawlable link should generally use an anchor element with an href:
- How can you determine whether important content is available in rendered HTML? Compare:
- How do JavaScript redirects affect SEO? For permanent URL changes, HTTP redirects are generally preferable because the redirect is communicated directly at the protocol level.
- How does Google process JavaScript-heavy websites? Google processes JavaScript applications through crawling, rendering and indexing.
- How would you audit a React, Next.js, Vue or Angular website for SEO? Audit the implementation, not the framework name.
- How would you diagnose a JavaScript SEO problem? Use a controlled comparison:
- What happens between Google's initial HTML fetch and JavaScript rendering? The initial HTTP response may contain complete content or only an application shell.
- What happens when server-rendered HTML differs from client-rendered HTML? Differences can be harmless or SEO-critical.
- When would you recommend SSR, CSR, SSG or hybrid rendering? Do not choose rendering architecture solely because one acronym sounds "more SEO friendly."
Redirects, Status Codes, Sitemaps & Robots
- How do redirect chains affect SEO and crawling? A chain such as:
- How do you handle conflicting canonical signals? Map all signals:
- How do you troubleshoot incorrect canonicalization at scale? Export:
- How would you handle thousands of URLs returning 200 but displaying "not found"? First determine whether they are true resources or generated error states.
- How would you identify redirect loops? A redirect loop occurs when:
- What happens when canonical tags point to 404 pages? The canonical target does not provide a valid representative page.
- What happens when canonical tags point to redirected URLs? This creates an unnecessary signal chain.
- What is the SEO impact of soft 404s? A soft 404 is a URL that technically returns a successful response but represents missing or nonexistent content.
- What would you check after a large-scale URL migration? Check:
- When should you use a 301 versus a 302? Use a permanent redirect when a URL has permanently moved.
Technical SEO Strategy & Foundations
- How do you balance technical SEO recommendations with development constraints? Start by defining the SEO requirement rather than prescribing one implementation.
- How do you define technical SEO at an organizational level? Technical SEO is the discipline of making a website reliably discoverable, crawlable, renderable, understandable and indexable while ensuring that the…
- How do you distinguish between an SEO problem and a website engineering problem? The same problem can be both.
- How do you measure the business impact of technical SEO? Connect technical changes to observable search and business outcomes:
- How do you prioritize technical SEO issues when there are hundreds of problems? Prioritize by search impact, business importance, scale, confidence and implementation effort, rather than by the number of warnings in a crawler.
- What does an advanced Technical SEO audit look like? An advanced audit begins with the website's architecture and business model, not with a crawler's warning list.
- What does technical SEO mean beyond crawling, indexing and fixing errors? Technical SEO is about how the website's architecture communicates with search engines.
- What is your process for deciding whether a technical SEO issue is worth fixing? First establish whether the issue is real, then determine its impact.
- What percentage of an SEO roadmap should be dedicated to technical SEO? There is no universal percentage.
- What technical SEO assumptions do experienced teams still get wrong? Common assumptions include:
URL Architecture, Internal Linking & Information Architecture
- Can excessive internal links dilute SEO signals? Google does not provide a simple numeric threshold saying that X links "dilute" SEO.
- How deep should important pages be within a site's architecture? There is no universal Google rule such as "every page must be within three clicks."
- How do you build an internal-linking strategy for a large website? Start with page importance and relationships.
- How do you identify internal-linking opportunities algorithmically? Create a page-to-page relevance model using:
- How do you identify orphan pages at scale? An orphan page is a URL that exists but has no useful internal link path to it.
- How do you measure the impact of an internal-linking change? Measure before/after changes in:
- How important are breadcrumbs for Technical SEO? Breadcrumbs can help communicate site hierarchy to users and search engines.
- How would you optimize internal links on an e-commerce website? Use multiple levels:
- How would you redesign the architecture of a website with thousands of disconnected pages? Start with page classification:
- What makes a scalable SEO-friendly URL architecture? A scalable architecture:
XML Sitemaps & Robots.txt
- How do sitemap errors help diagnose technical SEO problems? A sitemap can function as a controlled test set.
- How do you design XML sitemaps for millions of URLs? Use sitemap indexes and split URL sets into manageable sitemap files according to the sitemap protocol limits.
- How do you structure sitemap indexes for large websites? Group URLs by logical types where useful:
- How do you troubleshoot sitemap URLs that Google isn't indexing? For a sample:
- How would you safely change robots.txt on a high-traffic production website? Treat robots.txt as production-critical configuration.
- Should canonicalized URLs appear in XML sitemaps? Generally, the sitemap should list the preferred canonical URLs rather than duplicate variants.
- Should noindexed URLs appear in XML sitemaps? Avoid treating the sitemap as an inventory of URLs that you explicitly don't want indexed.
- What are common mistakes in robots.txt? Common mistakes include:
- What happens if a URL is blocked by robots.txt but included in an XML sitemap? The sitemap tells Google the URL exists, while robots.txt tells Google it cannot crawl the URL.
- What should and shouldn't be included in an XML sitemap? Include URLs you want search engines to discover and that represent the preferred versions of your content.
Machine-readable index: llms.txt. Add .md to any answer URL for a plain-Markdown version.