The DNS root key has changed: check resolution before diagnosing a traffic drop
IANA confirmed the October 11 root-key rollover. If a site fails to load, separate resolver validation, HTTP access and search reporting before blaming rankings.
Latest SEO stories
Latest SEO articles
Latest reporting on crawling, indexing and search performance.
-
-
Google’s UGC Fresh Data Program Is Not a Shortcut for News Articles
Google’s new UGC documentation explains an approval-only pipeline for public community content. Here is how to decide whether your platform fits.
-
Google Updates Its AI Content Guidance With Quality-Rater Checks
Google’s October 1 guidance update points publishers to separate page-level and site-scale tests for effort, originality, added value and user purpose.
-
Google’s SAFE paper does not explain the September Search spam update
Google’s SAFE paper studies coordinated synthetic-video channel abuse. It does not connect the system to Search ranking or the active September spam rollout.
-
Google Search Console adds multimodal web reporting.
Google now separates image-involved web searches in Search Console. Here is what the new filter measures, why queries are absent, and how to compare it with Image search and AI impressions.
-
Google begins September spam update with global rollout
Google says its September 2026 spam update is rolling out globally and across all languages. The rollout may take up to two weeks; Google has not identified a specific target.
-
Google Says Text Added With CSS Content May Not Be Indexed.
Google clarified that text inserted with the CSS content property sits outside the DOM and may not be indexed, so meaningful copy belongs in semantic HTML.
-
Schema.org 30.1 Product Fields Pass Google Parsing but Fail the Public Validator
A dated compatibility test of six Schema.org 30.1 commerce properties finds a lagging public validator, successful Google parsing and a nested Product risk.
-
Some Sites Report Bing Visibility Falling to Zero
Several site owners reported sudden zeroes in Bing Webmaster data after August 31. No official incident was found, so diagnosis must separate five possible failure paths.
From this desk
Further reading
Guides and practical resources for the questions behind the news.
Read the featured guide
Audit a new website in priority order
Clear indexing and template blockers before polishing lower-impact details. The audit framework shows the order and the evidence to record.
Audit
Find the first blocker
Check crawl access, indexability, page jobs, templates, performance, and measurement in a defensible order.
Launch
Release without guessing
Verify redirects, robots rules, canonicals, rendering, analytics, and rollback before a new site goes live.
Architecture
Give every page a distinct job
Build topic clusters around reader decisions, then keep, reposition, merge, or retire pages when their jobs overlap.
Publishing
Keep claims close to evidence
Use a reader job, claim ledger, source hierarchy, information-gain requirement, and maintenance trigger.
A useful standard
How to use this SEO library
Choose the page that matches the decision in front of you. Each answer distinguishes documented requirements from recommended practice and keeps uncertainty visible.
Exposure before polish
Resolve crawl, index, rendering, and template failures before spending time on refinements that search systems may never see.
One page, one job
Map each page to a reader decision so internal links, headings, and content depth support a clear purpose.
Measure at the right layer
Treat Search Console, analytics, crawls, and experiments as different evidence sources. None proves causation on its own.
References and next steps