Quick Takeaways (read this first)

• Google now recommends author.url for Article markup (Aug 6, 2026). Treat it as your author’s canonical machine identity on your site. See the update note in Latest Google Search documentation updates.
• Use a crawlable on-site author page URL—not LinkedIn/Twitter—as author.url. Consistency across every article matters more than perfection.
• Upgrade author pages to carry the entity: credentials, expertise scope, editorial role, and corroboration links. Then connect the dots: byline link + author.url + Organization publisher markup.
• Measure impact where it shows up: use Search Console’s Generative AI performance report and map AI impressions to authors weekly.
• Roll it out first on “answerable” pages in high-trust categories (health, finance, legal, safety)—the pages most likely to be summarized and attributed in AI answers.

What Google Changed (and why it’s bigger than it looks)

Google’s change is deceptively small: a recommended field in structured data. But it’s a signal about what search systems increasingly need to do reliably: resolve identity.

In Google’s documentation update log, Google notes that author.url is now recommended for Article structured data (Aug 6, 2026). That’s the kind of change that doesn’t trigger a “schema rush” on SEO Twitter—yet it’s exactly the sort of quiet shift that tends to matter for AI-era retrieval and grounding. (Reference: Google Search Central documentation updates.)

Why this matters for AEO/GEO (not just “SEO schema compliance”)

Classic SEO rewards pages. AEO/GEO rewards sources. And sources are usually entities (people, organizations, institutions) with stable identifiers.

When an answer engine generates a summary, it still needs to decide:

• Which sources to ground the answer on (who gets cited/linked/used as evidence)
• Which voice is trustworthy enough to quote or paraphrase
• Whether “Dr. Jane Smith” in one article is the same entity as “Jane Smith, MD” in another

Most sites mark up author.name. Many also have a byline. But a name alone is a weak identifier. Names collide. Titles vary. Formatting changes. That’s where author.url becomes an unusually high-leverage fix: it gives machines a stable, crawlable identity pointer.

author.url is an Entity Join Key (the non-obvious part)

Here’s the unique angle we’ve found matters in practice: author.url isn’t just another property. It’s a join key that helps systems merge signals across:

1. Your articles (claims, topics, freshness, citations)
2. Your author page (credentials, experience, editorial role, bio)
3. External corroboration (profiles, publications, licenses, speaking, research)

Contrarian insight: your author page matters more than your social profiles

A common implementation mistake is to set author.url to LinkedIn or X. That feels intuitive (“that’s where the author is real”), but it’s usually a weaker move for two reasons:

• You don’t control it. Profiles change, get rate-limited, or become inaccessible to crawlers.
• It breaks internal consolidation. Your site still needs a canonical author hub that all your content points to consistently.

Use your own author profile URL as the canonical identity, then link outward from there.

Good vs. bad identity resolution (quick examples)

• Bad: Article A uses “Jane Smith” (no URL), Article B uses “Jane Smith, MD” (no URL) → machines may treat them as different authors.
• Better: Both articles include author.url = https://example.com/authors/jane-smith → machines can merge author-level trust signals.
• Best: author.url is consistent, the byline links to the same page, and that author page links to credentials and corroboration → easier “who said it” grounding.

The 1‑Hour Implementation Plan (technical + editorial)

You can implement author.url quickly, but doing it correctly means you need both markup and a credible author page. Here’s the fastest safe rollout we recommend.

Step 1: Pick your canonical author URL pattern

Choose one stable, crawlable format and stick to it:

• /authors/{first-last} (common for publishers)
• /team/{first-last} (common for SaaS)
• /about/{first-last} (works, but avoid mixing with general “About” pages)

Rule: one author = one canonical URL. If you’re migrating, use a 301 redirect and update structured data over time.

Step 2: Ensure the author page is crawlable, indexable, and internally linked

This sounds basic, but it’s where many implementations fail. Before you touch schema:

• Confirm the author pages return 200 OK (not 404/soft-404).
• They are not blocked by robots.txt or noindex.
• Every article’s byline visibly links to the author page (not just in JSON-LD).

Step 3: Add author.url to your Article JSON-LD

Here’s a clean baseline snippet. (You can use JSON-LD; that’s what most teams ship.)

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Google added author.url to Article schema",
  "datePublished": "2026-08-10",
  "dateModified": "2026-08-10",
  "author": {
    "@type": "Person",
    "name": "Jane Smith",
    "url": "https://example.com/authors/jane-smith"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Media",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  }
}

Important details:

• Use the on-site author page as author.url (canonical, crawlable).
• Keep the author name consistent with the author page heading.
• If you have multiple authors, include an array of Person objects with distinct URLs.

Step 4: Add “corroboration links” on the author page (not in the Article markup)

Once author.url points to a page, that page becomes the entity hub. Make it do real work:

• Credentials: degrees, certifications, licenses (where appropriate)
• Experience: “10 years in B2B cybersecurity marketing,” “former clinical pharmacist,” etc.
• Editorial role: staff writer, reviewer, medical reviewer, fact-checker
• External profiles: LinkedIn, Google Scholar, PubMed, bar association listing, CFP registry, etc.
• Topic scope: 3–6 areas of expertise (helps prevent “author sprawl”)

This is also where you can include sameAs links (on the author page’s Person schema) if you want to strengthen external identity matching.

Step 5: Validate and ship safely

1. Run the page through Rich Results Test and/or Schema Markup Validator.
2. Check that the structured data rendered matches the canonical author URL (watch out for templating bugs).
3. Spot-check 10 URLs across categories: blog posts, guides, news, hub pages.
4. Deploy sitewide for one author first (pilot), then expand.

Google’s doc change is “recommended,” not “required.” That’s good news: you can implement without fear of breaking eligibility. But treat validation as a release checklist anyway.

3 Real-World Implementation Examples (good, better, best)

Example 1: SaaS company blog (B2B trust without “big publisher” signals)

Scenario: You run content marketing for a security SaaS. Your AI visibility problem isn’t ranking—it’s getting chosen as a grounding source when AI answers summarize “best practices” queries.

What we’d implement in 1 hour:

• Create /authors/alex-chen with a short bio: “Threat research lead, 8 years in incident response.”
• Add links to: LinkedIn + conference talk page + GitHub (if relevant).
• Update article template to add author.url pointing to that page and ensure the byline links to it.

Why it works: AI systems that need to answer “who said this?” can resolve Alex as a stable entity across multiple incident-response articles—rather than treating each post as a standalone anonymous page.

Common mistake: putting the company About page as the author URL for every post. That collapses author identity into brand identity and loses “expert voice” resolution.

Example 2: Healthcare publisher (YMYL + medical reviewer workflows)

Scenario: You publish medical explainers with both a writer and a medical reviewer. AI answers frequently demand expert attribution, especially for symptoms, dosages, and risk guidance.

Better-than-basic approach:

• Use author for the writer (with author.url to the writer page).
• Add a separate structured field for reviewer (often modeled as reviewedBy or editor depending on your schema strategy), and ensure the reviewer has their own canonical URL.
• On the reviewer page, include license type and jurisdiction when appropriate (e.g., “MD, California”).

Why it works: you’re not only making the author citable—you’re separating “who wrote” vs “who validated.” That maps better to how trust is evaluated in health content.

Example 3: Finance/legal lead-gen site (reducing “anonymous advice” risk)

Scenario: Your pages convert well, but AI summaries avoid citing you because your advice reads generic and your authorship is thin (or inconsistent).

Best practice rollout:

• Start with your top 20 “answerable” pages (definitions, comparisons, “best option for X”).
• Create canonical author pages for the subject-matter experts (CPA, CFP, attorney) and link to professional registries where possible.
• Add author.url consistently across those pages first, then expand to long-tail content.

Why it works: it’s a targeted trust upgrade. You’re improving the “who said it” layer specifically where AI systems are most likely to quote or paraphrase.

How to Measure Whether This Actually Improves AI Visibility

Schema changes can feel like “set it and hope.” Don’t do that. Google is making AI visibility more measurable, and you should use that to create a tight loop.

Use Search Console’s Generative AI report as your baseline

Google’s Generative AI performance report provides visibility into how your site appears in generative AI features in Search (note: the report focuses on impressions; interpret carefully).

Weekly author-level export (a simple but powerful workflow)

1. Export last 7 days of Generative AI report data (pages + impressions).
2. Join URLs to your CMS data (author id) or to on-page structured data extraction.
3. Group by author: total AI impressions, number of cited/visible URLs, and top queries (if available).
4. Compare before/after the rollout for pilot authors.

If you want a practical reading guide, Search Engine Journal has a helpful walkthrough on interpreting Google’s AI impressions reporting: Google Now Reports AI Search Impressions. Here’s How To Read Them.

Why this measurement loop is different from classic SEO reporting

In AEO/GEO, you’re often optimizing for “selection as a source,” not just clicks. Google has also been rolling out more controls and insights for site owners around AI surfaces; keep an eye on what’s available and how inclusion/exclusion is handled (reference: Google’s announcement on new opportunities, control and insights for website owners).

What success looks like:

• Your strongest expert authors account for a growing share of AI impressions.
• High-trust pages (medical/finance/legal explainers) get cited more often than generic blog posts.
• When you publish new content under a well-established author entity, it gets picked up faster.

Common Mistakes (that make author.url pointless)

Mistake 1: Using social URLs as the canonical author identity

As mentioned earlier, social links are great corroboration but a weak primary identifier. Use an on-site author page as author.url, then link out.

Mistake 2: Multiple author URLs for the same person

It’s common during rebrands or CMS migrations to end up with:

• /author/jane-smith
• /authors/jane-smith-md
• /team/jane-smith

Pick one canonical URL, 301 the rest, and update templates. Entity consolidation depends on consistency.

Mistake 3: Author pages that are thin, hidden, or noindexed

If the author page is a 150-word bio with no credentials and no internal links, you’ve created an identity pointer to an empty shell. AI systems will still struggle to answer “why trust this person?”

Mistake 4: No visible byline link

Relying only on JSON-LD is fragile. A visible byline link reinforces the relationship for users and machines and helps crawlers discover author pages naturally.

Mistake 5: Treating this like FAQ schema

This is not an “answer formatting” tactic. It’s an attribution and trust tactic. It complements your snippet formatting and citation-ready writing, like the approach we outlined in Google AI Mode citation-ready passages, but it solves a different problem: source identity.

FAQ: Practical Questions SEOs Ask About author.url

Is author.url required for rich results?

No—Google’s update frames it as recommended. But recommendations often indicate what Google wants to understand more reliably, especially as AI surfaces expand. The underlying update is documented in Search Central’s updates log.

Should author.url point to a Person schema page?

Ideally, yes: a canonical author profile page that includes a clear name, bio, and (optionally) Person structured data. The bigger requirement is that it’s consistent and crawlable.

What if we have “Editorial Team” instead of named authors?

If you’re in a high-trust category, this is a missed opportunity. Consider introducing named authors and reviewers at least on pages that are likely to be summarized by AI (definitions, comparisons, “best for X”). You can still have an editorial process page, but entity-level trust is easier to establish with real people.

Does this help beyond Google (Perplexity, ChatGPT, etc.)?

Often, yes—because the core problem is universal: entity resolution. A stable author hub page makes it easier for any system that crawls the web to connect your author across multiple articles and contexts. If you’re building cross-engine trust, also see our thinking on domain-level trust labels in Perplexity’s source labels and GEO trust.

How fast will we see results?

Expect variability. Schema is not a direct “ranking switch.” Treat this as a compounding trust improvement. The best approach is to ship it, then watch AI impressions and page inclusion patterns in the GSC Generative AI report weekly.

What to Do Next (Action Steps Checklist)

If you want the practical “do this today” version, here it is.

Today (60 minutes)

1. Pick canonical author URLs for your top 3 authors.
2. Ensure those author pages are indexable and internally linked from bylines.
3. Add author.url to your Article template and deploy for those authors.
4. Validate 10 pages (Rich Results Test / Schema Validator).

This week (2–3 hours)

• Upgrade author pages with credentials + topic scope + external corroboration links.
• Roll out to your top 20 “answerable” pages in YMYL-ish categories first.
• Set up a weekly export from Search Console’s Generative AI report and group by author.

This month (make it durable)

• Create an “author governance” rule: no new author goes live without a canonical profile page.
• Standardize naming (Jane Smith vs Jane Smith, MD) across bylines and schema.
• Run a quarterly audit to detect duplicate author URLs and redirect drift.

If you’re already running a citation audit loop, plug this into it. Our workflow in GSC’s Generative AI report: a 30‑minute citation audit loop pairs well with author-level entity checks—because you can quickly see whether your “trusted experts” are the ones being surfaced.

Make this measurable with aeotool.ai

At aeotool.ai, we’ve found the teams who win AI visibility treat attribution like an engineering problem: stable entities, consistent identifiers, and a weekly measurement loop.

If you want help operationalizing this, try our AEO tool dashboard and set up your author/entity checks alongside your AI visibility monitoring. Sign up here: https://aeotool.ai/register.

And install our Chrome extension for quick on-page audits (including structured data and machine-readable attribution signals): AEO Analyzer Chrome extension.