Reviews sitemap completeness, canonical URL configuration, hreflang pairing for bilingual sites, robots.txt directives, and Search Console signals before publishing a content batch. This is especially important for bilingual static sites where indexing misconfigurations can cause search engines to index the wrong locale or deprioritize pages unfairly.
Use cases
- Publishing a new bilingual (English/Chinese) content batch where hreflang tags must be correctly paired
- Switching a Cloudflare branch deployment to production and ensuring only the production URLs appear in the sitemap
- Updating the sitemap after a site restructure where URLs have changed and old URLs need redirect rules
- Debugging why a new page is not appearing in search results despite being included in the sitemap
- Before launching a major content update where you want to confirm no pages are inadvertently noindexed
Key features
- Verify the sitemap contains only production URLs and that each URL resolves with a 200 status, removing any staging or branch URLs
- Confirm canonical tags point to the preferred URL version and are consistent across all pages in the batch
- For bilingual sites, verify each page has correctly paired hreflang tags referencing both the English and Chinese versions
- Check robots.txt to ensure the sitemap is referenced and no indexing directives accidentally block important pages
- Submit the updated sitemap to Google Search Console and monitor the indexing report for any errors or warnings
When to Use This Skill
- When preparing to launch a new bilingual site or significant content update
- When debugging unexplained drops in search impressions or indexing regressions
- When switching deployment environments (staging to production) and needing to validate sitemap accuracy
Expected Output
An SEO indexing report confirming sitemap completeness, canonical correctness, hreflang pairing, and robots.txt directives, with any errors flagged for correction.
Frequently Asked Questions
- What is the most common SEO indexing mistake on bilingual static sites?
- Missing or incorrect hreflang tags causing search engines to serve the wrong language version to users, or canonical tags pointing to URLs that no longer exist after a deployment.
- Should search result pages or paginated archives be indexed?
- Generally no—use noindex,follow for search result pages and paginated archives to prevent search engines from indexing near-duplicate content that dilutes the visibility of canonical pages.
- How often should I check Search Console for indexing issues?
- Check within 48 hours of any significant content publish or deployment. Set up email alerts for critical indexing errors in Search Console so you are notified proactively rather than discovering issues through traffic drops.
Related
Related
3 Indexed items
SEO audit for web properties
Diagnoses indexing, crawlability, and on-page SEO issues across an entire site using automated crawls, Lighthouse checks, and structured output. An SEO audit surfaces actionable findings ranked by priority before manual review, making it possible to address critical issues quickly rather than discovering them through traffic drops.
Observability baselines
Establishes golden signals (latency, traffic, errors, saturation), SLO windows, and dashboard checks before agents automate deployments so that 'healthy' and 'degraded' have measurable definitions rather than subjective interpretations. This is essential when AI agents are managing deploys because agents need objective metrics to make decisions, not human gut feelings.
Agentic AI orchestration efficiency claims due diligence
Turns CEO and vendor narratives about agentic AI efficiency into a procurement and strategy checklist. The workflow separates quoted efficiency metrics (for example token- or energy-per-user framing) from product launch facts, orchestration architecture claims, and third-party valuation context in the same article. It references CNBC reporting on June 3, 2026 that Perplexity CEO Aravind Srinivas told CNBC's Elaine Yu the long-term AI winner will maximize what he called the "most taken value per watt per user" by balancing accuracy, latency, cost, privacy, and intelligence; that Perplexity is emphasizing agentic orchestration with Perplexity Computer (announced February) and Personal Computer on Windows (announced the prior Tuesday, with Mac already available); that Srinivas said Personal Computer routes processing between device and cloud; that Perplexity was last reportedly valued at $20 billion versus Anthropic near $1 trillion and OpenAI just over $850 billion with Anthropic confidentially filing for a U.S. IPO that week; and that Srinivas cited tripled annualized revenue since the start of the year tied to integrated Anthropic model improvements—without treating media valuations or CEO efficiency slogans as internal benchmarks.