Daily SEO Note — September 17, 2026: Google Search Profiles Open at 10,000 Followers

SEO for Content Writers

Today's most consequential editorial change is about access, not ranking. On September 16 Google cut the follower threshold for claiming a Search profile to 10,000 on a single supported platform, and published a guide for adding a Search profile badge to your own site. The ranking and spam systems, by contrast, did not move.

Search Profiles Now Open at 10,000 Followers

Google now requires a public profile with at least 10,000 followers on a single supported platform — Instagram, TikTok, YouTube, or X — to be eligible for a Search profile, per its creator eligibility page. The claimant must be at least 18, and Google's claim documentation states that one Google Account can manage up to 10 profiles before a second account is needed. The feature is live for United States publishers and creators, with Google saying it plans to expand to other countries later in the year.

This affects brand and author identity rather than any one content type. A Search profile gathers a publisher's or creator's output from their website and from connected social platforms into a single destination on Google, and when a user follows that profile the connected content becomes more likely to reach them in Google Discover. The profile is therefore a distribution asset that sits alongside the ranking systems rather than inside them.

The concrete instruction for your next cycle is to audit the masthead against the new bar. Any bylined author or brand account clearing 10,000 followers on one platform is now claimable, where at the previous thresholds most contributors were not. Nominate one Google Account as owner of record for up to ten profiles, and fold claiming into the author-page workflow instead of leaving it as an ad hoc social task.

Stop modelling Discover reach as a pure function of article-level quality signals. A followed profile is now an explicit input, which means author identity work carries a measurable distribution payoff rather than only an E-E-A-T one.

The Search Profile Badge Is a New Owned-Surface CTA

Alongside the threshold cut, Google published a guide for adding a Search profile badge to your website. You may use either an official badge image linking to your profile, or a plain text link reading "Find us on Google Search" pointing at the same profile URL. This is the first sanctioned route for converting existing site traffic into Search profile follows.

For editors this is a placement and wording decision, not a technical one. The badge competes for the same space as newsletter and social calls to action, and Google's guidance allows a higher-emphasis labelled button when it sits next to a Preferred Sources badge. Choose deliberately which one leads: Preferred Sources shapes what a reader sees in Top Stories, while the profile badge shapes Discover.

Add badge placement to the article template brief — the author bio block and the site footer are the obvious candidates — and write the surrounding microcopy yourself rather than shipping a bare logo. Do not alter the badge's colours or proportions; Google's design rules prohibit stretching, rotating, or recolouring the official asset.

Search Console Still Reports AI Links at Block Position

Google's generative AI performance reports in Search Console aggregate AI Overviews and AI Mode data, but they do not break out where a link sits inside an AI answer. Every link in an AI Overview inherits the position of the AI Overview block itself, the same way Google treats other search features.

On September 16 John Mueller said publicly that position and impression tracking for these surfaces will evolve as the surfaces themselves evolve. He gave no timeline and did not say whether historical data would be restated. Treat that as an unconfirmed forward-looking statement: the documented behaviour has not changed and no Google documentation was updated to reflect it.

Editorially this means an average-position figure on an AI row tells you the block placed well, not that your citation did. Stop writing performance narratives that infer citation prominence from position in the generative AI report, and work from impression and click deltas on the specific URLs instead.

Ranking Systems: No Verified Change

No core update, spam update, or Discover update started, progressed, or completed in the window: the Search Status Dashboard reported no incidents across crawling, indexing, ranking, and serving, and Google's core updates page lists no new rollout. Community chatter about volatility on September 15 remains unconfirmed and is excluded from the checklist below.

Apply to Your Next Brief

• Check every bylined author and brand account against the 10,000-follower bar on Instagram, TikTok, YouTube, or X, and claim what now qualifies.
• Nominate one Google Account as owner of record for up to ten Search profiles before anyone starts claiming ad hoc.
• Add a Search profile badge, or a "Find us on Google Search" text link, to the author bio block with microcopy you wrote.
• Decide per template whether the Preferred Sources badge or the Search profile badge takes the higher-emphasis slot.
• Remove average-position claims about AI Overviews from reporting templates and cite impressions and clicks per URL instead.
• Do not brief around a September core update. None has been confirmed.

SEO for Developers

The one change worth a same-day pull request is Schema.org 30.1, released September 16, which adds Digital Product Passport vocabulary that EU-facing commerce sites will need. Google's badge guide landed the same day with concrete markup requirements. Crawler, edge, and framework surfaces were flat.

Schema.org 30.1 Adds Digital Product Passport Vocabulary

Schema.org released version 30.1 on September 16. The release summary adds vocabulary supporting discovery of EU Digital Product Passports, introducing DigitalProductPassport, DeclarationOfConformity, and EnvironmentalProductDeclaration as subtypes of Certification, alongside vocabulary for common eCommerce product data. The release is non-breaking: existing markup keeps validating and nothing you ship today stops working.

The symptom of ignoring it is not an error but absence. EU regulatory product data stays invisible to any consumer that reads the vocabulary, including the compliance tooling this release exists to serve. Add the types on product pages where you already hold conformity or environmental declaration data.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Product",
  "sku": "SKU-1234",
  "hasCertification": {
    "@type": "DigitalProductPassport",
    "issuedBy": { "@type": "Organization", "name": "Example GmbH" },
    "url": "https://example.com/dpp/sku-1234"
  }
}
</script>

One caveat before anyone briefs this as a rich-result win: a Schema.org release is not Google feature eligibility. Google's structured data gallery lists the types it actually consumes and has not added these. Validate syntax with the Rich Results Test, but expect no new rich result from this release. Classification: important, watch.

Search Profile Badge: An Anchor, an SVG, and an Accessible Name

Google's Search profiles documentation, last updated September 16, specifies the badge as an anchor pointing at your profile URL wrapping an official SVG from Google's badge asset package, with alt text and an aria-label. A plain text link reading "Find us on Google Search" to the same URL is the supported fallback. It is non-breaking, and there is no structured data component: this is a link, not markup Google parses.

<a
  href="https://profile.google.com/@yourhandle"
  aria-label="Find us on Google Search"
  class="gsp-badge"
>
  <img
    src="/assets/google-search-profile-badge.svg"
    alt="Find us on Google Search"
    width="180"
    height="48"
  />
</a>

The constraint most likely to fail review is the touch target: Google requires at least 48 by 48 dp on Android and 44 by 44 px on iOS and the web, so a badge scaled down to fit a dense footer will be non-compliant. Do not recolour, stretch, or rotate the asset, and do not mix monochrome and colour badges in the same layout.

Guard Your Dashboards Against Block-Level AI Position Data

If you pipe Search Console data into BigQuery or a dashboard, the position field on generative AI rows reflects the AI Overview block, not the rank of your citation inside the answer. Any alert thresholded on position change for those rows is measuring block placement and will page you for the wrong reason.

Google stated on September 16 that this tracking will change over time, with no timeline and no accompanying documentation update. That makes it a watch item rather than a ship item. Do not rewrite the pipeline yet, but label AI-surface rows distinctly in your warehouse now so a future definition change cannot silently corrupt a blended average, and filter them out of any position-based regression monitor.

Crawler, Edge, and Framework Surfaces: No Verified Change

Nothing shipped in these surfaces inside the window. Google's common crawlers documentation still carries a July 14, 2026 last-updated date, with no change to Google-Extended or any AI fetcher token. The Cloudflare changelog's only September 16 entry was Hyperdrive support for Python Workers, with nothing touching bot rules, WAF, or robots handling. The Vercel changelog carried no redirect, rewrite, middleware, ISR, or cache entries. Next.js published only 16.4 canaries; the last stable release was 16.3.5 on September 11, outside the window.

Ship Today

1. Add DigitalProductPassport markup to product pages that already hold conformity or environmental declaration data, then validate with the Rich Results Test.
2. Once the profile is claimed, ship the Search profile badge as an anchor with an aria-label and a compliant 44 px minimum touch target.
3. Tag generative AI rows in your Search Console warehouse export and exclude them from position-based regression alerts.