most SEO news is noise. a few things actually move rankings and revenue each week
Rank Season sends just those every Monday: what moved in Google and AI search, the AI workflows that rank, and the plays that turn clicks into money
free. first issue drops soon, get on the list: rankseason.com
Google's Indexing API is not a faster way to get blog posts indexed.
per Google's quickstart, it can only be used for pages with JobPosting, or BroadcastEvent embedded in a VideoObject. so job listings and livestream pages, nothing else.
the same doc says every submission goes through spam detection, and using multiple accounts or other tricks to get past the quota can get your access revoked.
default quota, per the quota page Google updated in October:
- 200 publish requests per day per project, URL_UPDATED and URL_DELETED combined
- 180 getMetadata requests per minute
- 380 requests per minute across all endpoints
- free to use, daily quota resets at midnight Pacific
the Indexing API check:
1. list what your plugin or script sends through it
2. anything that isn't a job listing or livestream page: stop sending it
3. normal pages: keep your sitemap current and link new pages from pages Google already crawls
4. job sites: send URL_DELETED when a listing comes down, not only URL_UPDATED
source: Google Search Central Indexing API docs.
limits: this is what the docs say. it doesn't show what Google does with requests outside those page types.
anyone still pushing blog posts through it?
your core update drop probably isn't ready to read yet.
the November 2026 core update started Nov 10, and Google's Search Status Dashboard still shows no end date. the last five core updates listed there took between 11 days 21 hours and 18 days 2 hours to finish.
Google's core updates doc sets the order:
- confirm on the dashboard that the rollout finished
- wait at least a full week after it completes
- then compare that week with a week before the rollout started
the core update read:
1. save the week before Nov 10 (Nov 3 to 9) as your baseline
2. when the dashboard shows an end date, add 7 days before you judge anything
3. compare top pages and queries, not just the sitewide line
4. small moves, like position 2 to 4: Google says no drastic action, and avoid changing pages that already do well
5. large drops, like 4 to 29: a deeper look at the site as a whole
6. check Web, Images, Video and News separately
my take: hold off on rewrites while it's still rolling. positions can keep moving until it ends.
limits: past durations don't predict this one. it's a timeline, not a forecast.
which week are you using as your baseline?
3
3
172
underscores in your URLs? Google still recommends hyphens.
Google's URL structure doc, updated in October, says to use hyphens (-) instead of underscores (_) to separate words. its reason: underscores often mean "keep these together", like format_date in code, while hyphens clearly mark a word boundary.
two more lines in the same doc that audits often skip:
- URLs are case sensitive. Google treats /APPLE and /apple as different URLs with their own content
- trim parameters that don't change the content
the URL check, before your next launch or migration:
1. new URLs: words split with hyphens, one consistent case
2. if your server returns the same page for upper and lower case, convert to one case, as Google suggests
3. strip parameters that don't change what's on the page
what I'd skip: renaming live underscore URLs just for this. the doc doesn't tell you to, and every rename needs a redirect. that's my call, not Google's.
limits: this is a recommendation in Google's docs, not a ranking test.
hyphens or underscores on your sites right now?
if you want Google doc changes like this explained, Rank Season is the free monday SEO newsletter. first issue drops soon, and the list gets exclusive access to a link trading community. link in bio
3
120
AI content licensing is starting to price each use separately: training, RAG, grounding, AI-generated overviews.
the Internet Licensing Collective launched Nov 12 with Yahoo Scout as its first commercial licensee. it's a nonprofit (formerly RSL Collective), and its launch release says more than 3000 media brands, content owners and publishing platforms are in.
how it works, per that release:
- one blanket license for AI companies, who license only the uses they need
- publishers join free and choose which uses and which AI companies they approve
- non-exclusive, so existing direct deals stay
- payouts weighted by how the content is used, the value of the AI product, and how often it's relied on, not catalog size
my read: "block AI or allow it" is turning into a per-use decision. Google's shared AI training control for robots.txt, announced Oct 30, covers training only.
the use split check:
1. list the uses: training, answers that pull your pages, AI-generated overviews
2. decide yes or no for each one, not one blanket rule
3. make sure your robots.txt says the same thing
limits: one licensee so far and no payout figures published. too early to call it worth joining.
would you allow AI answers but block training?
3
2
98
thinking about opting your site out of AI Overviews? read your data first, and maybe not this week.
Google's Search generative AI control is live for every site (Search Console > Settings > Search generative AI). exclude, and your links and content stop showing in AI Overviews, AI Mode and generative AI features in Discover. Google says it isn't a ranking signal for the rest of Search.
the opt-out math check:
1. check the setting on every property. child properties inherit from the parent, so one change at the domain level can flip all of them
2. open the Generative AI performance report and pull clicks and impressions for your top pages
3. leave out Nov 9 to 11 (Google flagged a logging error that undercounted impressions) and wait for the November core update to finish
4. know what it doesn't do: it doesn't stop AI training. that's Google-Extended
5. if you flip it, annotate the date. Google says exclusion takes 1 to 2 days, some content longer
what would make you opt out?
7
5
202
your PageSpeed score isn't what Search Console grades you on.
the Core Web Vitals report uses real Chrome user data (CrUX), not a lab test. per Google's docs:
- it reads the 75th percentile of page loads over the last 28 days
- it grades groups of similar pages, not single URLs
- a group's status is its worst metric. poor CLS with good INP is still poor
- good means LCP 2.5s or less, INP 200ms or less, CLS 0.1 or less
and Lighthouse can't measure INP at all. no real user, no real clicks. web.dev says to use Total Blocking Time there instead.
the field data check:
1. open the Core Web Vitals report, mobile first
2. note which metric fails and which URL group it hits
3. open an example URL in PageSpeed Insights and read the real user section, not the lab score
4. fix the template behind the group, not one page
5. group missing from the report? it may not have enough Chrome data yet. that isn't a pass
keep the ranking part honest too. Google says good Core Web Vitals don't guarantee top rankings, and chasing a perfect score just for SEO "may not be the best use of your time."
source: Google Search Central and web.dev docs.
which metric fails on your mobile report?
your sitemap index can be valid XML and still list sitemaps Google won't accept.
Google's rule: every sitemap an index lists must sit in the same folder as the index, or deeper.
index at example.com/blog/sitemap_ind…:
- example.com/blog/posts.xml works
- example.com/products.xml doesn't
the sitemap index check:
1. open the index and note its folder
2. compare every <loc> to that folder. anything higher up, or on another host, is a miss
3. move the index to the root, or set up cross-site submission if the sitemaps live on another host
4. while you're in there: each sitemap max 50,000 URLs or 50MB uncompressed, each index max 50,000 sitemaps
source: Google Search Central sitemap docs.
limits: this checks one rule from Google's docs. it doesn't tell you why pages aren't indexed.
where does your sitemap index live?
1
2
76
bought an expired domain for its backlinks? Google's spam policy cares what you do with it, not how old it is.
Google's spam policies define expired domain abuse: buying an expired domain and repurposing it mainly to manipulate rankings with content that gives users little to no value.
Google's own examples:
- affiliate content on a former government agency site
- commercial medical products on a former nonprofit medical charity site
- casino content on a former elementary school site
every example is a topic swap. that's my reading of the list, not a rule Google published.
the expired domain check, before you buy:
1. look up what the domain hosted before, in the Wayback Machine
2. compare it to what you plan to publish. same audience, or a swap like the ones above?
3. ask if anyone would find the site except through Google. Google says these domains usually aren't meant to be found any other way
4. if the old reputation is the main reason you're buying, skip it
Google also says it's fine to use an old domain for a new, original site built for people first.
limits: Google gives no test or threshold. this check reads its examples, it doesn't predict rankings.
ever bought a domain mainly for its old links?
if you'd rather earn links than borrow an old domain's past, Rank Season is the free monday SEO newsletter. first issue drops soon, and the list gets exclusive access to a link trading community. link in bio
4
5
203
most AI visibility reports count mentions. a mention isn't a pick.
Gaetano DiNardi's Search Engine Land piece (Nov 13) leans on a framework from Alisa Scharf at Seer Interactive that splits the two: share of voice is how often AI names you. recommendation rate is how often AI picks you when it makes a pick.
those numbers can split hard. you can be named in most answers and picked in almost none, stuck in the "also worth a look" line.
the pick rate check:
1. pull 10 buyer questions from real sales calls, with the context buyers give: company size, budget, current stack
2. run each one several times. answers change run to run
3. mark every answer: not named, named, or picked
4. also mark if the facts about you are right
5. picked divided by all answers is your pick rate. named but rarely picked? check if your pages say plainly who you're best for
how many of your AI mentions are actual picks?
ChatGPT now shows businesses their mentions and website clicks. read OpenAI's definitions before those numbers go in a report.
Businesses in ChatGPT launched Nov 10 in beta. after you claim your business in Business Hub and pass Persona ID verification, Insights shows the past 28 days. from OpenAI's help page:
- mention, online business: ChatGPT references your website. your brand name alone doesn't count
- mention, local business: a result for your location shows, even if nobody opens it
- discovery topics: themes from answers that cited you, not the prompts people typed
- blank metric: can mean below the reporting threshold or still collecting, not zero
and the clicks tooltip (screenshot shared by Barry Schwartz at Search Engine Roundtable): recorded link clicks, they don't confirm website visits or conversions.
call it the definition check:
1. claim it (phone, business email, DNS TXT record or Shopify) and finish Persona. insights stay locked until then
2. label it "ChatGPT mentions (site referenced)" in reports, not brand mentions
3. put ChatGPT clicks next to the sessions your analytics shows from ChatGPT, and expect a gap
4. treat a blank as unknown, not zero
5. note the numbers each month if you want a trend, since the view is a rolling 28 days
limits: beta, aggregated, and these are OpenAI's own counts. a click here isn't proof of a visit, and a mention isn't a recommendation.
have you claimed your business in ChatGPT yet?
8
6
275
if your site lets users make public pages, Google updated its user-generated spam guide on Oct 26 with a default worth copying.
from the doc: pages people create to share by link, generated outputs, and tools that aren't meant to be found in Search should get noindex (meta tag or X-Robots-Tag) or a robots.txt block by default.
why it matters: spammers use open platforms to mass publish pages, and those pages can end up indexed under your domain.
the share link check:
1. list every feature that creates a public URL: profiles, shared results, exports, comments
2. for each one ask: is this meant for Search, or only for people with the link?
3. link only: noindex by default
4. new users with no reputation: Google suggests noindex on their posts until they earn trust
5. links in untrusted content: nofollow or ugc
6. watch Page Indexing and Performance in Search Console for spikes in indexed pages or queries that don't fit your site
limits: this is Google's guidance, not a ranking study. Google doesn't say how big the risk is for any one site.
source: Google Search Central, Prevent user-generated spam (updated Oct 26)
if you run SEO for a SaaS or a platform, Rank Season is my free monday SEO newsletter. it hasn't launched yet, so you'd be early, and the list gets exclusive access to a link trading community. link in bio
how many features on your site create a public URL?
1
2
145
Search Console Performance report: chart total higher than the sum of the Queries table?
Search Console Help lists two reasons that gap is expected:
1. the table shows max 1,000 rows, so rare and long-tail rows can sit in the chart total but not the table
2. anonymized rare queries are left out of the query table, but stay in the chart totals unless you add a query filter
so don't treat the table sum as your real total. report the chart number.
and if you filter by query, expect the total to drop. that's the anonymized rows leaving, not lost traffic.
have you ever chased a chart vs table gap that was just this?
2
2
132
impressions flat. clicks down almost half, overnight.
that's one site in France after Google turned on AI Overviews there on July 22. Glenn Gabe shared Search Console data from 5 sites:
- one went from about 750 to 400 clicks a day, CTR 2% to 1.1%
- a YMYL site went from about 80 to 25 a day
- another YMYL site saw CTR drop from 1.2% to 0.4%, with a second drop around Aug 13
- two sites barely moved
his own caveat: 5 sites, and timing alone doesn't prove AI Overviews caused it.
my read: "AI Overviews killed my traffic" and "AI Overviews don't matter" are both lazy takes. your own data shows which group you're in.
the flat impressions check, 15 minutes:
1. in Search Console, filter to one country and note when AI impressions start in the generative AI report
2. compare clicks, impressions and CTR for 4 weeks before vs after
3. split brand and non-brand queries
4. flag pages where impressions held but CTR fell
5. search the top 3 by hand and see if you're cited
which group is your site in?
8
5
242
an OpenAI content deal doesn't mean ChatGPT cites the publisher. so don't pick digital PR targets off the partner list.
Ryan Law at Ahrefs checked 85 OpenAI partner domains in Brand Radar against 5.5 million US ChatGPT answers (November snapshot). answers citing each:
- Vogue: 42,108
- Car and Driver: 41,603
- The Atlantic: 724
- Politico: 10
Ahrefs puts it plainly: a partnership makes a publisher eligible to appear, it doesn't guarantee it. the most cited partners are mostly review and lifestyle sites, not news sites.
call it the citation pitch check, before a PR push aimed at AI visibility:
1. list the publishers you'd pitch for one topic
2. check how often ChatGPT already cites each one in your niche (Brand Radar, or your own prompt log)
3. pitch the ones already cited for your topic first. Ahrefs' advice: use the partner list only to break ties
4. judge over weeks, not one day. in tracking Ahrefs cites, only about a quarter of pages cited for a prompt were cited again the next day
limits: US data only, one snapshot, and these are citation counts, not traffic. a placement on a cited site still isn't proof your brand shows up in answers.
if you want off-page plays like this every monday, that's Rank Season. free, it hasn't launched yet so you'd be early, and the list gets exclusive access to a link trading community. link in bio
which publisher in your niche would you check first?
1
2
152
Google AI Overviews are making AI images on the fly again, for some searchers.
Barry Schwartz replicated it today after Derek Hobson spotted it. it works in some browsers. in others the AI Overview still says "I cannot generate images directly." Google hasn't announced anything new.
quick history: Google added image generation to AI Overviews in July, then stopped it in August after recipe creators pushed back. Robby Stein called it "a small experiment we're no longer running."
if your traffic comes from how-to or recipe searches, watch this one. my read: a generated picture can answer the "what does it look like" part before anyone clicks.
the image swap check, 10 minutes:
1. search your top 5 how-to queries in a clean browser
2. screenshot the AI Overview and note if it shows a generated image
3. check if your own photos and link still appear
4. repeat next week, it's rolling out unevenly
if it does show up, lean on what a generator can't fake: your own photos, steps you actually tested, a short video.
seen one on your queries yet?
5
2
116
Google put Gemini 4 Hydrogen into Search for all users yesterday. Google calls it the biggest model upgrade to Search yet.
the part that matters for SEO, from Google's own post: Hydrogen "supercharges" query fan-out. Search splits one question into simultaneous queries across the relevant subtopics, and Google says that connects people to a broader range of links than before.
so what gets cited is closer to one subtopic than one keyword.
the fan-out coverage check, for one money query:
1. write the long version a real buyer would type, with all its parts
2. list the subtopics each part splits into
3. find the page on your site that answers each one directly. a section inside a big guide counts if it answers fast
4. any subtopic with no answer is a gap your rank tracker won't show
limits: Google didn't say which subtopics it generates or how links get picked. this is my reading of the announcement, not a tested result. and don't credit Hydrogen alone for any shift this week. the November core update is still rolling out, and Search Console's Generative AI report undercounted Nov 9 to 11.
source: Google Search blog, Robby Stein, Nov 12
if you want AI search changes turned into steps like this, Rank Season is my free monday SEO newsletter. it hasn't launched yet, so you'd be early, and the list gets exclusive access to a link trading community. link in bio
how many parts does your top query usually have?
Google confirmed a Search Console bug: the Generative AI performance report undercounted impressions for Nov 9 to Nov 11.
Google calls it a logging error that affects data logging only. your real visibility in AI Overviews and AI Mode didn't change.
the timing is bad. the November core update started Nov 10, right inside those dates. easy to blame the update for a dip that's only missing data. Barry Schwartz flagged the overlap too.
the bug date check:
1. in the Generative AI report, treat Nov 9 to 11 as bad data
2. compare the week before Nov 9 with the days after Nov 11, skip the gap
3. judge the core update on clicks in the regular Performance report, not on AI impressions
4. after the August bug, Google restored the missing data a few days later. re-check those dates next week before you send a final report
did your AI impressions dip this week?
7
3
244
Google Search visits showing up as direct or referral in your analytics? Google just documented how its Referer header works, and some of the leaks are on your own site.
from the new Search Central page (Nov 12):
- Google Search uses the origin referrer policy. the Referer is only the Google host, the .com or a local country domain. no path, no query, so it never tells you the search term
- Google Images and Discover send the same values, so a Referer match counts them with web search
- the Google app on Android can send an android-app value instead of the web domain
- the Referer can be blank: private browsing, some browsers when you open a result in a new tab, privacy extensions, a native search widget handing off to a browser
call it the referer leak check:
1. review custom channel rules, referral exclusions and filters. Google says these can reclassify Search visits as referral or direct
2. test your redirects. a JavaScript or meta refresh redirect can replace the Referer with your own URL, and a redirect that sends a stricter Referrer-Policy can remove it
3. in raw logs, count only landing page requests. images, CSS and JS requests carry your own page as the Referer
4. add the Android app value to any custom match rule
limits: this won't match Search Console 1:1. Search Console counts the click, analytics counts a page load that ran the tracking code, and Search Console leaves out Ads clicks. use Search Console for queries, the Referer for "did Google send this visit"
which would you check first, channel rules or redirects?
3
2
209


