VI · GEO / SEO / Schema — Daily Operational Report

Generated 2026-06-04 08:31 server time · rebuilds daily · 3 sites · every change snapshotted & tracked 7 days · click any box to drill down

Today at a glance

8 clicks 28d (±0)116 impressions 28d (±0)2 fixes today9 fixes tracked totalOAuth live

Changes made on your behalf — with before/after, why, 7-day outcome

DateSiteTypeBeforeAfterWhyOutcome (proof)
2026-06-04davidalyons.comsitemap_generatedno sitemap.xml or wp-sitemap.xmlgenerated sitemap.xml with 7 URLsNo sitemap = crawlers find pages only by following links, missing orphans and new content for days/weeks.tracking (0/7d)
2026-06-04vehementlyinked.comfaqpage_schema_addedno FAQPage schema (AI engines had no Q&A to extract)injected FAQPage JSON-LD with 4 Q&A pairsFAQPage schema is the format Google's AI Overviews / SGE and other answer engines extract verbatim. Each Q&A pair gives them a ready-made answer to cite about you — and the answers embed your disambiguation (literary fiction, not the other SYNCD).tracking (0/7d)
2026-06-04syncdtrilogy.comllms_txt_regeneratedllms.txt missing disambiguation/unified-ISBN blockwrote canonical llms.txt with full catalog + disambiguationAI engines fetch llms.txt before answering questions about you. The disambiguation block explicitly tells them you are NOT the other SYNCD/other VI — directly attacks the mistaken-identity problem at the AI-context layer.tracking (0/7d)
2026-06-04vehementlyinked.comllms_txt_regeneratedllms.txt missing disambiguation/unified-ISBN blockwrote canonical llms.txt with full catalog + disambiguationAI engines fetch llms.txt before answering questions about you. The disambiguation block explicitly tells them you are NOT the other SYNCD/other VI — directly attacks the mistaken-identity problem at the AI-context layer.tracking (0/7d)
2026-06-04davidalyons.comllms_txt_regeneratedllms.txt missing disambiguation/unified-ISBN blockwrote canonical llms.txt with full catalog + disambiguationAI engines fetch llms.txt before answering questions about you. The disambiguation block explicitly tells them you are NOT the other SYNCD/other VI — directly attacks the mistaken-identity problem at the AI-context layer.tracking (0/7d)
2026-06-03syncdtrilogy.comschema_id_unified13 Person/Organization entities had no @idinjected canonical @id URIs into 13 schema entitiesWithout @id, Google treats every schema mention of "David A. Lyons" or "Vehemently Inked" as a separate entity. Canonical @id URIs merge them into one knowledge-graph node so all ranking signals consolidate to the same identity.28d impr: 31 → 31 (+0) [1/7d]
2026-06-03syncdtrilogy.comsearchaction_addedno WebSite/SearchAction schema on homepageinjected WebSite @id + SearchAction JSON-LD before </head>SearchAction unlocks the Google sitelink searchbox in SERPs and gives Google a canonical WebSite entity to attach all other schema to. No brand wording change — pure structural enrichment.28d impr: 31 → 31 (+0) [1/7d]
2026-06-03vehementlyinked.comsearchaction_addedno WebSite/SearchAction schema on homepageinjected WebSite @id + SearchAction JSON-LD before </head>SearchAction unlocks the Google sitelink searchbox in SERPs and gives Google a canonical WebSite entity to attach all other schema to. No brand wording change — pure structural enrichment.28d impr: 0 → 0 (+0) [1/7d]
2026-06-03davidalyons.comsearchaction_addedno WebSite/SearchAction schema on homepageinjected WebSite @id + SearchAction JSON-LD before </head>SearchAction unlocks the Google sitelink searchbox in SERPs and gives Google a canonical WebSite entity to attach all other schema to. No brand wording change — pure structural enrichment.28d impr: 94 → 85 (-9) [1/7d]

Trend over time — is any of this working?

What this is: every daily run appends a snapshot. This is the longitudinal view — the only honest measure of whether the fixes move the needle. Watch the direction, not any single day.

DateTotal clicksTotal imprdavidalyons pos: "david a lyons"syncdtrilogy pos: "syncd"
2026-06-038172548
2026-06-038 (±0)172548
2026-06-038 (±0)125548
2026-06-038 (±0)125548
2026-06-038 (±0)125548
2026-06-038 (±0)125548
2026-06-038 (±0)125548
2026-06-038 (±0)125548
2026-06-038 (±0)125548
2026-06-038 (±0)125548
2026-06-038 (±0)125548
2026-06-048 (±0)116548
2026-06-048 (±0)116548
2026-06-048 (±0)116548
2026-06-048 (±0)116548
2026-06-048 (±0)116548
2026-06-048 (±0)116548
2026-06-048 (±0)116548

As fixes land (FAQ schema, llms.txt disambiguation, schema @id, SearchAction), watch the brand-term positions climb and impressions rise here over the coming weeks. Flat or falling for 2+ weeks after a fix = that fix did not work, and its row in the changes table turns red.

Per-site drill-down

Backlink + citation discovery — sites mentioning you (real outreach targets)

What this is: a daily web search for sites that already mention you by name. Sites that mention you but don't link are the lowest-friction outreach in SEO — you're not pitching a stranger, you're asking someone who already cited you to make the citation clickable.

How to use it: For each row marked NO — outreach target: 1) Click the host link to see how they mentioned you. 2) Find a contact form / email / Twitter on that site. 3) Send a 2-line message: "Saw you mentioned [book title] in [context]. Would you be open to linking it to [your URL]? Helps readers find it." 4) Most positive-mention sites say yes. Track which ones land — those become repeat-coverage targets for future books.

No new mentions surfaced in this scan (will retry tomorrow).

Book-catalog presence — every ISBN across every platform

What this is: per-ISBN deep check across Open Library, Google Books, Apple Books, Kobo, Barnes & Noble, WorldCat, and Goodreads. Each platform = a discovery surface + (where it indexes you) a permanent backlink. Library systems pull from Open Library + WorldCat. Apple/Kobo/B&N are the non-Amazon retail discovery.

How to fix any MISSING cell: Open Library → openlibrary.org add book (5 min). Google Books → Partner Center (10 min). Apple Books → distribute via IngramSpark/Draft2Digital (or direct via iTunes Connect). Kobo → Kobo Writing Life. Barnes & Noble → B&N Press or via Ingram. WorldCat → automatic once your book is in OCLC (request via Ingram). Goodreads → librarian-add at goodreads.com/book/new.

TitleISBNOLGoogle BooksAppleKoboB&NWorldCatGoodreads
Cryptoamnesia979-8992756418
Cryptoanomaly979-8992756449
Cryptogenesis979-8992756463
SYNCD (unified)979-8-9927564-9-4

Internet Archive / Wayback Machine — historical snapshot health

What this is: Wayback Machine archives every public site over time. AI engines (and journalists, librarians, academics) use it as the canonical "what did this site say on date X" reference. A well-archived site has stronger citation credibility.

How to use it: If snapshot count is low or last snapshot is >30 days old, manually trigger fresh snapshots at web.archive.org/save — paste each site URL, click save. Free. Takes 30 seconds per site. The next daily report will show updated count.

SiteTotal snapshotsLast snapshotAction
davidalyons.com02026-04-17 (48 days ago)save fresh snapshot →
vehementlyinked.com02026-04-13 (52 days ago)save fresh snapshot →
syncdtrilogy.com02026-04-17 (48 days ago)save fresh snapshot →

Search-engine inclusion — beyond Google + Bing

What this is: probe 8 independent search engines (Brave, Mojeek, Yep, Marginalia, Kagi public, You.com, Ecosia, Startpage) for whether your domain appears at all. Each ✗ = a discovery surface you don't exist on.

How to fix: Brave/Mojeek/Yep — submit via their webmaster panels (free). Marginalia — automatic once you have inbound links from quality sources. Kagi — focused on quality content + structured data (your AI-readiness work feeds this). Ecosia/Startpage proxy Bing/Google — fixing your Bing/Google presence fixes these.

SiteBraveMojeekYepMarginaliaKagi (public)You.comEcosiaStartpage
davidalyons.com
vehementlyinked.com
syncdtrilogy.com

Competitive SERP analysis — who outranks you for your terms

What this is: for each of your key brand terms, the top SERP results — showing your position (if any) and which other sites are sitting on the real estate you want.

How to use it: If your site doesn't appear in the top 5, the competitors listed ARE the sites you need to outrank. Click each — see what they've done that you haven't (length, structure, schema, internal link depth). The fastest move: target striking-distance queries those competitors don't cover, then expand laterally into theirs.

"syncd" — you are at: NOT in top 30

"SYNCD trilogy" — you are at: NOT in top 30

"David A. Lyons" — you are at: NOT in top 30

"Vehemently Inked" — you are at: NOT in top 30

"Cryptoamnesia novel" — you are at: NOT in top 30

Wikidata deep audit — per-entity claim coverage + missing-entity hunt

What this is: Wikidata is the public, machine-readable knowledge graph that powers AI engines (Claude, GPT, Perplexity, Gemini) and Google's Knowledge Panel. Every fact about you that's in Wikidata gets repeated across every AI engine. Every missing claim is information they don't have about you.

How to use it: For each missing claim row, click "add on entity →". You'll land on the Q-ID page with that property pre-selected. Paste the value (the column tells you what kind of value goes there). Save. Wikidata propagates to AI engines within 1-2 weeks. For missing entities at the bottom: click "create new item →", set label + description, then add the listed P-claims. Recommended order: 1) Create David A. Lyons Person entity first. 2) Add P50 (author) claim on each existing book entity pointing to David's new Q-ID. 3) Then create individual Cryptoamnesia / Cryptoanomaly / Cryptogenesis Q-IDs. 4) Link them to trilogy series Q139311362 via P361 (part of).

Q139311193 Vehemently Inked LLC — organization · 8 claims · 0 sitelinks · coverage 70%

Description: independent book publisher based in Tulsa, Oklahoma

Aliases: Vehemently Inked, VI Press

External IDs: website=https://vehementlyinked.com

Missing propWhat to addEdit link
P1454legal formadd on entity →
P1716brand nameadd on entity →
P5008on focus list of Wikimediaadd on entity →

Q139311362 SYNCD Trilogy — book_series · 8 claims · 0 sitelinks · coverage 75%

Description: experimental fiction novel series by David A. Lyons, published by Vehemently Inked LLC

Aliases: SYNCD, SYNCED Trilogy, Synced Trilogy, The SYNCD Trilogy, SYNCD Trilogy, Synchronization trilogy

External IDs: website=https://syncdtrilogy.com

Missing propWhat to addEdit link
P407language of workadd on entity →
P648Open Library IDadd on entity →

Q139830174 Synchronization — book · 13 claims · 0 sitelinks · coverage 67%

Description: novel by David A. Lyons

Aliases: SYNCD (unified edition), SYNCD unified, SYNCD unified edition, SYNCD

External IDs: OpenLibrary=OL45371300W ISBN-13=979-8-9927564-9-4

Missing propWhat to addEdit link
P1104number of pagesadd on entity →
P2969Goodreads IDadd on entity →
P244Library of Congressadd on entity →
P437distribution formatadd on entity →
P5331OCLCadd on entity →

Missing entities — should they exist?

Should exist (search query)What it would beSearch resultAction
David A. Lyons authorPerson — author identity (separate from VI org). Properties: P31:Q5 human, P106 author, P800 notable work pointing to SYNCD, external IDs (OpenLibrary, Goodreads, ISNI, VIAF).NOT FOUND (0 unrelated hits)create new item →
Cryptoamnesia LyonsBook — trilogy vol 1 (ISBN 979-8992756418). Properties: P31 book, P50 author, P179 SYNCD Trilogy, P212 ISBN-13, P577 publication date, P123 publisher.NOT FOUND (0 unrelated hits)create new item →
Cryptoanomaly LyonsBook — trilogy vol 2 (ISBN 979-8992756449). Same schema.NOT FOUND (0 unrelated hits)create new item →
Cryptogenesis LyonsBook — trilogy vol 3 (ISBN 979-8992756463). Same schema.NOT FOUND (0 unrelated hits)create new item →
davidalyons.com — Author identity 8 YOUR clicks 85 YOUR impr 2 buried 7/8 tech 3 WRONG-PERSON queries filtered 1 HIGH 2 AUTO
Technical state — 7/8 green · schema: 4 blocks (0 invalid) · HTTP 200
CheckState
HTTP status200
index.html last edited2026-06-03 07:36
TitleDavid A. Lyons - Author
Meta descriptionpresent
Canonical tagpresent
OpenGraph tagspresent
Twitter cardpresent
robots.txtpresent
AI crawlers allow-listed8 / 8
SitemapMISSING
llms.txtpresent
JSON-LD schema blocks4 total, 0 invalid parse
Schema @typesQuestion×17, Answer×17, Book×7, PostalAddress×5, WebSite×4, Organization×3, Person×2, Place×2, FAQPage×2, ImageObject×1, GeoCoordinates×1, BookSeries×1, CreativeWorkSeries×1, SearchAction×1, EntryPoint×1
IndexNow ping todayHTTP 200 accepted
Search Console — last 28 days — 8 clicks · 85 impr · 4 on page 1 · 100% branded
8 clicks85 impressions6 distinct queriesPage 1: 4Page 2: 0Buried: 2Branded: 100%

Brand-term ranking

TermPositionImprClicks
david a lyons5 page 1298
david a. lyons3 page 1400
david lyons author8 page 140
david lyonsNOT RANKING

Top 15 queries you appear for

QueryImprClkCTRPos
david a. lyons4000%3
david a lyons29827.6%5
david a lyons author900%2
david lyons author400%8
david b lyons200%39
lyons david100%47

Top pages by impressions

PageImprClk
davidalyons.com/2988
davidalyons.com/home/1121
davidalyons.com/#about10
davidalyons.com/#art10
davidalyons.com/#books10
davidalyons.com/#gallery10
davidalyons.com/cryptogenesis/20
davidalyons.com/hello-world/10
davidalyons.com/270
WordPress full audit + REST writes — 4 pages · 2 posts · audited 12 · 5 have issues · REST writes: NO AUTH (audit only)

Every published WP page+post enumerated via REST. Audited up to 30 per site. Where auth works, this routine pushes meta-description fixes via REST directly. Issues = anything off-spec.

URLHTTPCanonOG-TOG-IMGMetaDescJSON-LDH1img no-altWords
davidalyons.com/2001954103554
davidalyons.com/home/2001394104860
davidalyons.com/#about2001954103554
davidalyons.com/#art2001954103554
davidalyons.com/#books2001954103554
davidalyons.com/#gallery2001954103554
davidalyons.com/cryptogenesis/2002204610
davidalyons.com/hello-world/4040000
davidalyons.com/books/2002204738
davidalyons.com/cryptoanomaly/2002204605
davidalyons.com/cryptoamnesia/2002204693
davidalyons.com/10-2/2001393104796
Sitemap crawl — broken-link check — 9 URLs in sitemap · 9 checked · 0 broken

All checked URLs in sitemap return 200. Crawl budget intact.

GA4 engagement — last 28 days — 1 users · 1 sessions · 100% engaged · avg 13.2s
Metric28-day value
Total users1
Sessions1
Engaged sessions1 (100% engagement rate)
Avg session duration13.2s
Page views1
Technical health — robots, security headers, language — security headers 1/5 · robots ok · lang set
CheckStateWhy it matters
robots.txt existsWithout it, crawlers guess. With it, you control crawl + declare sitemap.
robots blocks everythingnoDisallow: / on User-agent: * = your whole site is blocked from indexing. Catastrophic if accidental.
robots declares sitemapSitemap: line in robots.txt is how crawlers without prior knowledge find your sitemap.
HSTS headerStrict-Transport-Security — forces HTTPS, minor ranking + trust signal.
X-Content-Type-OptionsPrevents MIME-sniffing attacks; part of security-score signals.
Content-Security-PolicyDefense-in-depth; not a direct ranking factor but part of site-quality signals.
X-Frame-OptionsClickjacking protection.
<html lang> attributeTells search + AI engines your content language. Missing = ambiguous targeting.
UTF-8 charset declaredPrevents character-encoding garble in SERP snippets.
Image SEO — alt text + lazy-load audit — 29 images · 0 missing alt · 0 lazy-loaded
MetricCountWhy it matters
Total <img> tags29Each is a potential discovery surface via Google Images.
With descriptive alt29Properly alt-tagged = indexed in image search + accessibility compliant.
Empty alt=""0Empty alt is correct ONLY for decorative images. Otherwise it kills image-search visibility.
Missing alt attribute entirely0Worst case — invisible to search + breaks accessibility. Fix: add alt="[descriptive text]" to every <img>.
lazy-loaded0loading="lazy" improves LCP. Below-fold images should have it; above-fold should not.
sameAs link verification — does every Wikidata/OpenLibrary/etc URL in your schema actually resolve? — 20 URLs checked · 5 broken

Broken sameAs URLs in schema = Google distrusts your knowledge-graph claims. Fix each one or remove from schema.

sameAs URLHTTP
https://www.goodreads.com/author/show/56310972.David_A_Lyons200
https://www.amazon.com/author/davidalyons405
https://books.apple.com/us/author/david-a-lyons/id6744961715404
https://davidalyons.substack.com200
https://vehementlyinked.com200
https://www.wikidata.org/wiki/Q139182557200
https://openlibrary.org/authors/OL3714334A200
https://www.goodreads.com/book/show/229558260-cryptoamnesia200
https://www.amazon.com/dp/B0F1XW7TDS405
https://openlibrary.org/works/OL45366980W200
https://www.wikidata.org/wiki/Q139185676200
https://www.goodreads.com/book/show/235796478-cryptoanomaly200
https://www.amazon.com/dp/B0FC5TPK2C405
https://openlibrary.org/works/OL45371292W200
https://www.wikidata.org/wiki/Q139311652200
https://www.goodreads.com/book/show/249420804-cryptogenesis200
https://www.amazon.com/dp/B0GM6VBFKT405
https://openlibrary.org/works/OL45371294W200
https://www.wikidata.org/wiki/Q139312285200
https://davidalyons.com/200
AI Mode / AI Overviews — appearance + readiness — 0 AI-overview impressions · 0 clicks · readiness 3/6

What this is: Google launched AI Overviews / AI Mode in Search Console as a new "search appearance" type. When Google's SGE cites your URL in an AI-generated answer, that impression shows up here under an AI-flagged appearance value. Below: the raw breakdown by every searchAppearance type GSC returned, plus a per-site audit of whether your homepage is structured the way AI Overviews picks pages from.

How to use it: If "AI overview impressions" is 0, Google has never cited you in an AI answer yet. Fix the readiness checks below and the HIGH/MED AI plan items — they are the on-page signals Google's SGE looks for. Once readiness reaches 5-6/6 and you ship FAQ schema + H2 questions, AI Overview impressions typically start appearing in 4-8 weeks.

Search appearance breakdown

GSC returned no search-appearance breakdown for this site yet.

AI-readiness audit

SignalStateWhy it matters for AI Mode
FAQPage schema✓ presentAI Overviews preferentially extracts from FAQPage Q&A pairs.
Article schema✗ missingAI Mode cites Article-schema pages with author+datePublished as authoritative.
HowTo schema✗ missingHowTo = direct-answer for procedural queries.
QAPage schema✓ presentQAPage = explicit question-answer format AI engines parse.
Speakable markup✗ missingMarks passages voice-AI surfaces read aloud.
Author byline✓ presentE-E-A-T signal AI engines weight higher.
datePublished✓ presentFreshness signal — without it content reads as undated.
dateModified✗ missingLast-updated date — affects whether AI engines pull from you vs newer sources.
<h2> questions on page0AI engines scan H2 questions as direct-answer candidates. Target 3-8.

How to actually get cited in AI Mode (specific steps)

  1. Add FAQPage schema with 5-8 Q&A pairs — highest-leverage AI Overview signal. Questions like "What is SYNCD about?", "Who is David A. Lyons?", "What order should I read the SYNCD trilogy in?", "What genre is SYNCD?", "Where can I buy SYNCD?"
  2. Wrap evergreen pages in Article schema with author (linking to David A. Lyons Person Wikidata Q-ID once created), datePublished, dateModified in ISO 8601 format.
  3. Make sure llms.txt is current — AI engines fetch it before answering. Auto-regen queued.
  4. Apply to Search Console Insights / AI Mode beta at search.google.com/search-console/insights — Google rolls out the dedicated AI Mode performance report by waitlist. Beta access just shows the data sooner; on-page work above doesn't require it.
  5. Apply to Google Discover via Publisher Center — Discover and AI Mode share signals (Article schema, dates, authorship). Approved Discover sources weight higher in AI Overviews.
Google's view of your homepage (URL Inspection API) — verdict: PASS · last crawl: 2026-05-26 · 1 rich results detected
SignalGoogle's answer
Indexing verdictPASS
Coverage stateSubmitted and indexed
Indexing stateINDEXING_ALLOWED
Last crawl by Google2026-05-26T11:46:06Z
Page fetch stateSUCCESSFUL
robots.txt stateALLOWED
You declared canonicalhttps://davidalyons.com/
Google picked canonicalhttps://davidalyons.com/ match
Mobile usabilityVERDICT_UNSPECIFIED
Rich results detected1 types
Core Web Vitals & PageSpeed — mobile perf: /100 · LCP - · CLS -
ScoreMobileDesktop
Performance/100/100
SEO (Lighthouse)/100/100
Accessibility/100-

Core Web Vitals (mobile)

MetricValueThreshold
LCP (Largest Contentful Paint)-< 2.5s
CLS (Cumulative Layout Shift)-< 0.1
FCP (First Contentful Paint)-< 1.8s
TBT (Total Blocking Time)-< 200ms
INP (Interaction to Next Paint)-< 200ms

Full report: pagespeed.web.dev

Identity collisions — queries that are NOT about you — 3 shown · 44 impr / 0 clicks wasted on wrong-person searches

What this is: Google shows YOUR URL for searches about other Davids, other Vehemently Inkeds, other SYNCDs. Each row is impressions you "earned" but for the wrong reason — they don't convert and they pollute your real ranking signal.

How to fix the underlying problem: You can't fix individual queries — these are downstream of the bigger disambiguation issue. The root fixes: 1) Build the Person Q-ID for David A. Lyons in Wikidata (see Wikidata section above) so AI engines have a distinct node. 2) Add Person+Organization schema with sameAs Wikidata + OpenLibrary URLs on every site (auto-fix queued). 3) Build inbound brand-anchor links so your site is the strongest "David A. Lyons author" signal in Google's graph. 4) Track this list weekly — when collision impressions drop, your disambiguation is working.

Query (not yours)ImprClkPosWhy it is not yours
david lyons author at oneframework3508no brand marker matched
david lyons one framework editor8010no brand marker matched
metafictional meathead1046no brand marker (Lyons/SYNCD/VI) — likely about someone else
Ranking opportunities — striking distance — 2 queries at positions 4–20

Queries you ALREADY appear for. Ranked by impact-of-moving-up (impressions × gap to page 1).

QueryImprClkPosGapRecommended move
david a lyons2985page 1snippet/title tune to lift CTR
david lyons author408page 1snippet/title tune to lift CTR
Plan to rank up — 9 actions · 1 HIGH · 2 AUTO · 7 need you

Each row tells you the action, why it matters in your specific situation, the exact steps to do it, and whether the routine will handle it automatically or you have to.

HIGH
Own brand term david lyons
NEEDS YOU
Why this matters for you: You don't rank at all for it. The page exists but Google has no signal linking this term to your URL.
Steps: 1) Edit your homepage. 2) Open Yoast SEO panel. 3) Set SEO Title to start with david lyons followed by your current title. 4) Add the term verbatim in the first H1 and first paragraph. 5) In schema, add a WebSite block with name=david lyons. 6) From your two sister sites, add one inline link with anchor text david lyons. 7) Save and wait 2-4 weeks for Google to recrawl + re-rank.
MED
Enhance page ranking for david a lyons
NEEDS YOU
Why this matters for you: Pos 5 / 29 impr — search demand exists, you're already visible, just need to climb.
Steps: 1) Find the page Google currently shows for this query — see Top pages table. 2) Edit that page. 3) Title: include david a lyons near the start. 4) Add a 150-word section that directly answers the question this query implies. 5) Save. 6) Daily IndexNow ping will trigger re-crawl within 24h.
MED
Enhance page ranking for david lyons author
NEEDS YOU
Why this matters for you: Pos 8 / 4 impr — search demand exists, you're already visible, just need to climb.
Steps: 1) Find the page Google currently shows for this query — see Top pages table. 2) Edit that page. 3) Title: include david lyons author near the start. 4) Add a 150-word section that directly answers the question this query implies. 5) Save. 6) Daily IndexNow ping will trigger re-crawl within 24h.
MED
Add cold-discovery content
NEEDS YOU
Why this matters for you: 100% of your impressions are from people who already typed your name. Zero cold discovery — no one is finding you by typing a topic that interests them.
Steps: 1) Pick 3 topics adjacent to your work (e.g. "ergodic fiction", "House of Leaves successor", "AI-as-narrator novels", "Tulsa literary press"). 2) For each, write a 1000-word post on your blog/Substack covering it. 3) Cross-link to your books from within each post. 4) Submit each post URL via IndexNow (the daily routine will pick them up if added to sitemap). 5) Expect first impressions in 2-3 weeks.
MED
Add Article schema to evergreen pages
NEEDS YOU
Why this matters for you: AI Overviews cites Article-schema pages with author + datePublished + dateModified as authoritative sources. Without Article schema, your pages compete in the un-attributed bucket.
Steps: 1) For each substantial page (about, book pages, essays), wrap content in Article JSON-LD with: headline, author (@id linking to David Person entity), datePublished, dateModified, publisher (@id linking to VI Org). 2) Use ISO 8601 dates. 3) Cite source URLs where claims have sources. 4) Recrawl via IndexNow.
MED
Add 3-5 <h2> questions to homepage
NEEDS YOU
Why this matters for you: AI engines scan H2 questions as candidate prompts to answer. Pages with <h2>What is X?</h2> structure get parsed as direct-answer sources.
Steps: 1) Add an "FAQ" section to your homepage. 2) Use <h2> for each question (questions readers actually ask). 3) Follow each <h2> with a 40-60 word <p> that directly answers it. 4) Same Q&A pairs feed the FAQPage schema (HIGH priority above).
MED
Mobile usability verdict: VERDICT_UNSPECIFIED.
NEEDS YOU
Why this matters for you: Mobile-first index — non-mobile-friendly pages get downranked across all devices.
LOW
Generate sitemap.xml
AUTO (daily)
Why this matters for you: No sitemap = crawlers don't see your new/updated pages until they happen across an internal link.
AUTO: tomorrow's run will generate sitemap.xml from your WP REST page+post list and ping Bing/Yandex/Naver via IndexNow.
LOW
Add speakable schema marker
AUTO (daily)
Why this matters for you: Speakable schema tells Google Assistant + voice-AI surfaces which parts of your page to read aloud. Direct signal for voice-answer inclusion.
AUTO: tomorrow's run will add SpeakableSpecification to the WebSite schema pointing at your main hook paragraph.
vehementlyinked.com — Publisher / imprint 0 YOUR clicks 0 YOUR impr 0 buried 8/8 tech 1 WRONG-PERSON queries filtered 4 HIGH 1 AUTO
Technical state — 8/8 green · schema: 3 blocks (0 invalid) · HTTP 200
CheckState
HTTP status200
index.html last edited2026-06-03 07:36
TitleVehemently Inked — Independent Publishing Studio
Meta descriptionpresent
Canonical tagpresent
OpenGraph tagspresent
Twitter cardpresent
robots.txtpresent
AI crawlers allow-listed8 / 8
Sitemapsitemap.xml
llms.txtpresent
JSON-LD schema blocks3 total, 0 invalid parse
Schema @typesBook×4, WebSite×4, PostalAddress×3, Organization×2, Person×2, ScholarlyArticle×2, Place×1, CreativeWorkSeries×1, Offer×1, SearchAction×1, EntryPoint×1
IndexNow ping todayHTTP 200 accepted
Search Console — last 28 days — 0 clicks · 0 impr · 0 on page 1 · 0% branded
0 clicks0 impressions0 distinct queriesPage 1: 0Page 2: 0Buried: 0Branded: 0%

Brand-term ranking

TermPositionImprClicks
vehemently inkedNOT RANKING
vehemently inked publishingNOT RANKING
vehemently inked llcNOT RANKING

Top 15 queries you appear for

QueryImprClkCTRPos

Top pages by impressions

PageImprClk
vehementlyinked.com/624
vehementlyinked.com/publishing-news/71
vehementlyinked.com/#author10
vehementlyinked.com/#bcf10
vehementlyinked.com/#catalog10
vehementlyinked.com/#studio10
vehementlyinked.com/contact/20
vehementlyinked.com/for-writers/400
vehementlyinked.com/privacy-policy/20
vehementlyinked.com/home250
WordPress full audit + REST writes — 17 pages · 1 posts · audited 22 · 10 have issues · REST writes: NO AUTH (audit only)

Every published WP page+post enumerated via REST. Audited up to 30 per site. Where auth works, this routine pushes meta-description fixes via REST directly. Issues = anything off-spec.

URLHTTPCanonOG-TOG-IMGMetaDescJSON-LDH1img no-altWords
vehementlyinked.com/2002153103700
vehementlyinked.com/publishing-news/2003103477
vehementlyinked.com/#author2002153103700
vehementlyinked.com/#bcf2002153103700
vehementlyinked.com/#catalog2002153103700
vehementlyinked.com/#studio2002153103700
vehementlyinked.com/contact/2001562103964
vehementlyinked.com/for-writers/2003103414
vehementlyinked.com/synchronization/2003204025
vehementlyinked.com/my-account/2002103371
vehementlyinked.com/checkout/20021010551
vehementlyinked.com/cart/20021010551
vehementlyinked.com/shop/2002103545
vehementlyinked.com/books/2002203768
vehementlyinked.com/books/cryptogenesis/2001582203701
vehementlyinked.com/books/cryptoanomaly/2001622203696
vehementlyinked.com/books/cryptoamnesia/2001692203808
vehementlyinked.com/juno/2002103352
vehementlyinked.com/commentary/2001442104106
vehementlyinked.com/about-david-a-lyons/2001643204358
vehementlyinked.com/privacy-policy/2001332103634
vehementlyinked.com/hello-world/2002103403
Sitemap crawl — broken-link check — 7 URLs in sitemap · 7 checked · 0 broken

All checked URLs in sitemap return 200. Crawl budget intact.

GA4 engagement — last 28 days — 73 users · 102 sessions · 27% engaged · avg 65.6s
Metric28-day value
Total users73
Sessions102
Engaged sessions28 (27% engagement rate)
Avg session duration65.6s
Page views124
Technical health — robots, security headers, language — security headers 1/5 · robots ok · lang set
CheckStateWhy it matters
robots.txt existsWithout it, crawlers guess. With it, you control crawl + declare sitemap.
robots blocks everythingnoDisallow: / on User-agent: * = your whole site is blocked from indexing. Catastrophic if accidental.
robots declares sitemapSitemap: line in robots.txt is how crawlers without prior knowledge find your sitemap.
HSTS headerStrict-Transport-Security — forces HTTPS, minor ranking + trust signal.
X-Content-Type-OptionsPrevents MIME-sniffing attacks; part of security-score signals.
Content-Security-PolicyDefense-in-depth; not a direct ranking factor but part of site-quality signals.
X-Frame-OptionsClickjacking protection.
<html lang> attributeTells search + AI engines your content language. Missing = ambiguous targeting.
UTF-8 charset declaredPrevents character-encoding garble in SERP snippets.
Image SEO — alt text + lazy-load audit — 8 images · 0 missing alt · 0 lazy-loaded
MetricCountWhy it matters
Total <img> tags8Each is a potential discovery surface via Google Images.
With descriptive alt8Properly alt-tagged = indexed in image search + accessibility compliant.
Empty alt=""0Empty alt is correct ONLY for decorative images. Otherwise it kills image-search visibility.
Missing alt attribute entirely0Worst case — invisible to search + breaks accessibility. Fix: add alt="[descriptive text]" to every <img>.
lazy-loaded0loading="lazy" improves LCP. Below-fold images should have it; above-fold should not.
sameAs link verification — does every Wikidata/OpenLibrary/etc URL in your schema actually resolve? — 20 URLs checked · 3 broken

Broken sameAs URLs in schema = Google distrusts your knowledge-graph claims. Fix each one or remove from schema.

sameAs URLHTTP
https://www.wikidata.org/wiki/Q139182557200
https://openlibrary.org/authors/OL3714334A200
https://davidalyons.com/200
https://vehementlyinked.com/200
https://syncdtrilogy.com/200
https://vehementlyinked.substack.com/200
https://substack.com/@davidalyonsauthor200
https://www.amazon.com/author/davidalyons405
https://www.goodreads.com/author/show/56310972.David_A_Lyons200
https://books.apple.com/us/author/david-a-lyons/id6744961715404
https://www.instagram.com/the_house_of_lyons/429
https://www.wikidata.org/wiki/Q139311193200
https://www.wikidata.org/wiki/Q139311362200
https://syncedtrilogy.com/200
https://www.wikidata.org/wiki/Q139185676200
https://openlibrary.org/works/OL45366980W200
https://www.wikidata.org/wiki/Q139311652200
https://openlibrary.org/works/OL45371292W200
https://www.wikidata.org/wiki/Q139312285200
https://openlibrary.org/works/OL45371294W200
AI Mode / AI Overviews — appearance + readiness — 0 AI-overview impressions · 0 clicks · readiness 2/6

What this is: Google launched AI Overviews / AI Mode in Search Console as a new "search appearance" type. When Google's SGE cites your URL in an AI-generated answer, that impression shows up here under an AI-flagged appearance value. Below: the raw breakdown by every searchAppearance type GSC returned, plus a per-site audit of whether your homepage is structured the way AI Overviews picks pages from.

How to use it: If "AI overview impressions" is 0, Google has never cited you in an AI answer yet. Fix the readiness checks below and the HIGH/MED AI plan items — they are the on-page signals Google's SGE looks for. Once readiness reaches 5-6/6 and you ship FAQ schema + H2 questions, AI Overview impressions typically start appearing in 4-8 weeks.

Search appearance breakdown

GSC returned no search-appearance breakdown for this site yet.

AI-readiness audit

SignalStateWhy it matters for AI Mode
FAQPage schema✗ missingAI Overviews preferentially extracts from FAQPage Q&A pairs.
Article schema✗ missingAI Mode cites Article-schema pages with author+datePublished as authoritative.
HowTo schema✗ missingHowTo = direct-answer for procedural queries.
QAPage schema✗ missingQAPage = explicit question-answer format AI engines parse.
Speakable markup✗ missingMarks passages voice-AI surfaces read aloud.
Author byline✓ presentE-E-A-T signal AI engines weight higher.
datePublished✓ presentFreshness signal — without it content reads as undated.
dateModified✗ missingLast-updated date — affects whether AI engines pull from you vs newer sources.
<h2> questions on page0AI engines scan H2 questions as direct-answer candidates. Target 3-8.

How to actually get cited in AI Mode (specific steps)

  1. Add FAQPage schema with 5-8 Q&A pairs — highest-leverage AI Overview signal. Questions like "What is SYNCD about?", "Who is David A. Lyons?", "What order should I read the SYNCD trilogy in?", "What genre is SYNCD?", "Where can I buy SYNCD?"
  2. Wrap evergreen pages in Article schema with author (linking to David A. Lyons Person Wikidata Q-ID once created), datePublished, dateModified in ISO 8601 format.
  3. Make sure llms.txt is current — AI engines fetch it before answering. Auto-regen queued.
  4. Apply to Search Console Insights / AI Mode beta at search.google.com/search-console/insights — Google rolls out the dedicated AI Mode performance report by waitlist. Beta access just shows the data sooner; on-page work above doesn't require it.
  5. Apply to Google Discover via Publisher Center — Discover and AI Mode share signals (Article schema, dates, authorship). Approved Discover sources weight higher in AI Overviews.
Google's view of your homepage (URL Inspection API) — verdict: PASS · last crawl: 2026-06-03 · 0 rich results detected
SignalGoogle's answer
Indexing verdictPASS
Coverage stateSubmitted and indexed
Indexing stateINDEXING_ALLOWED
Last crawl by Google2026-06-03T13:14:31Z
Page fetch stateSUCCESSFUL
robots.txt stateALLOWED
You declared canonicalhttps://vehementlyinked.com/
Google picked canonicalhttps://vehementlyinked.com/ match
Mobile usabilityVERDICT_UNSPECIFIED
Rich results detected0 types
Core Web Vitals & PageSpeed — mobile perf: /100 · LCP - · CLS -
ScoreMobileDesktop
Performance/100/100
SEO (Lighthouse)/100/100
Accessibility/100-

Core Web Vitals (mobile)

MetricValueThreshold
LCP (Largest Contentful Paint)-< 2.5s
CLS (Cumulative Layout Shift)-< 0.1
FCP (First Contentful Paint)-< 1.8s
TBT (Total Blocking Time)-< 200ms
INP (Interaction to Next Paint)-< 200ms

Full report: pagespeed.web.dev

Identity collisions — queries that are NOT about you — 1 shown · 1 impr / 0 clicks wasted on wrong-person searches

What this is: Google shows YOUR URL for searches about other Davids, other Vehemently Inkeds, other SYNCDs. Each row is impressions you "earned" but for the wrong reason — they don't convert and they pollute your real ranking signal.

How to fix the underlying problem: You can't fix individual queries — these are downstream of the bigger disambiguation issue. The root fixes: 1) Build the Person Q-ID for David A. Lyons in Wikidata (see Wikidata section above) so AI engines have a distinct node. 2) Add Person+Organization schema with sameAs Wikidata + OpenLibrary URLs on every site (auto-fix queued). 3) Build inbound brand-anchor links so your site is the strongest "David A. Lyons author" signal in Google's graph. 4) Track this list weekly — when collision impressions drop, your disambiguation is working.

Query (not yours)ImprClkPosWhy it is not yours
david baccini books105no brand marker (Lyons/SYNCD/VI) — likely about someone else
Plan to rank up — 8 actions · 4 HIGH · 1 AUTO · 7 need you

Each row tells you the action, why it matters in your specific situation, the exact steps to do it, and whether the routine will handle it automatically or you have to.

HIGH
Own brand term vehemently inked
NEEDS YOU
Why this matters for you: You don't rank at all for it. The page exists but Google has no signal linking this term to your URL.
Steps: 1) Edit your homepage. 2) Open Yoast SEO panel. 3) Set SEO Title to start with vehemently inked followed by your current title. 4) Add the term verbatim in the first H1 and first paragraph. 5) In schema, add a WebSite block with name=vehemently inked. 6) From your two sister sites, add one inline link with anchor text vehemently inked. 7) Save and wait 2-4 weeks for Google to recrawl + re-rank.
HIGH
Own brand term vehemently inked publishing
NEEDS YOU
Why this matters for you: You don't rank at all for it. The page exists but Google has no signal linking this term to your URL.
Steps: 1) Edit your homepage. 2) Open Yoast SEO panel. 3) Set SEO Title to start with vehemently inked publishing followed by your current title. 4) Add the term verbatim in the first H1 and first paragraph. 5) In schema, add a WebSite block with name=vehemently inked publishing. 6) From your two sister sites, add one inline link with anchor text vehemently inked publishing. 7) Save and wait 2-4 weeks for Google to recrawl + re-rank.
HIGH
Own brand term vehemently inked llc
NEEDS YOU
Why this matters for you: You don't rank at all for it. The page exists but Google has no signal linking this term to your URL.
Steps: 1) Edit your homepage. 2) Open Yoast SEO panel. 3) Set SEO Title to start with vehemently inked llc followed by your current title. 4) Add the term verbatim in the first H1 and first paragraph. 5) In schema, add a WebSite block with name=vehemently inked llc. 6) From your two sister sites, add one inline link with anchor text vehemently inked llc. 7) Save and wait 2-4 weeks for Google to recrawl + re-rank.
HIGH
Add FAQPage schema with direct Q&A
NEEDS YOU
Why this matters for you: AI Overviews / AI Mode preferentially pulls from pages with FAQPage schema — the format Google's SGE was trained to extract verbatim. Without it, your site is invisible to the AI Overviews answer surface.
Steps: 1) Pick 5-8 questions readers actually ask about your work (e.g. "What is SYNCD about?", "What order should I read the trilogy in?", "Who is David A. Lyons?", "What genre is SYNCD?", "Where can I buy SYNCD?"). 2) Add a Q&A section to your homepage with each question as an <h2> and answer as a <p> (40-60 words, factual, definitive). 3) Wrap in FAQPage JSON-LD schema (next daily run can auto-inject if you tell me the Q&A pairs to use). 4) Recrawl within 24h via IndexNow.
MED
Add Article schema to evergreen pages
NEEDS YOU
Why this matters for you: AI Overviews cites Article-schema pages with author + datePublished + dateModified as authoritative sources. Without Article schema, your pages compete in the un-attributed bucket.
Steps: 1) For each substantial page (about, book pages, essays), wrap content in Article JSON-LD with: headline, author (@id linking to David Person entity), datePublished, dateModified, publisher (@id linking to VI Org). 2) Use ISO 8601 dates. 3) Cite source URLs where claims have sources. 4) Recrawl via IndexNow.
MED
Add 3-5 <h2> questions to homepage
NEEDS YOU
Why this matters for you: AI engines scan H2 questions as candidate prompts to answer. Pages with <h2>What is X?</h2> structure get parsed as direct-answer sources.
Steps: 1) Add an "FAQ" section to your homepage. 2) Use <h2> for each question (questions readers actually ask). 3) Follow each <h2> with a 40-60 word <p> that directly answers it. 4) Same Q&A pairs feed the FAQPage schema (HIGH priority above).
MED
Mobile usability verdict: VERDICT_UNSPECIFIED.
NEEDS YOU
Why this matters for you: Mobile-first index — non-mobile-friendly pages get downranked across all devices.
LOW
Add speakable schema marker
AUTO (daily)
Why this matters for you: Speakable schema tells Google Assistant + voice-AI surfaces which parts of your page to read aloud. Direct signal for voice-answer inclusion.
AUTO: tomorrow's run will add SpeakableSpecification to the WebSite schema pointing at your main hook paragraph.
syncdtrilogy.com — Book hub 0 YOUR clicks 31 YOUR impr 2 buried 8/8 tech 1 WRONG-PERSON queries filtered 5 HIGH 1 AUTO
Technical state — 8/8 green · schema: 25 blocks (0 invalid) · HTTP 200
CheckState
HTTP status200
index.html last edited2026-06-03 08:01
TitleSYNCD Trilogy | Experimental Literary Fiction by David A. Lyons
Meta descriptionpresent
Canonical tagpresent
OpenGraph tagspresent
Twitter cardpresent
robots.txtpresent
AI crawlers allow-listed8 / 8
Sitemapsitemap.xml
llms.txtpresent
JSON-LD schema blocks25 total, 0 invalid parse
Schema @typesBook×57, Person×29, Organization×25, Question×16, Answer×16, BookSeries×8, WebSite×6, Thing×5, Place×3, Offer×3, WebPage×3, CreativeWorkSeries×2, FAQPage×2, PostalAddress×2, SearchAction×1, EntryPoint×1
IndexNow ping todayHTTP 200 accepted
Search Console — last 28 days — 0 clicks · 31 impr · 0 on page 1 · 100% branded
0 clicks31 impressions2 distinct queriesPage 1: 0Page 2: 0Buried: 2Branded: 100%

Brand-term ranking

TermPositionImprClicks
syncd48 BURIED30
syncd trilogyNOT RANKING
cryptoamnesiaNOT RANKING
cryptoanomalyNOT RANKING
cryptogenesisNOT RANKING

Top 15 queries you appear for

QueryImprClkCTRPos
syncd cs2800%37
syncd300%48

Top pages by impressions

PageImprClk
syncdtrilogy.com/497
syncdtrilogy.com/10
WordPress full audit + REST writes — 0 pages · 1 posts · audited 3 · 1 have issues · REST writes: NO AUTH (audit only)

Every published WP page+post enumerated via REST. Audited up to 30 per site. Where auth works, this routine pushes meta-description fixes via REST directly. Issues = anything off-spec.

URLHTTPCanonOG-TOG-IMGMetaDescJSON-LDH1img no-altWords
syncdtrilogy.com/20013225107241
syncdtrilogy.com/20013225107241
syncdtrilogy.com/hello-world/2000105451
Sitemap crawl — broken-link check — 1 URLs in sitemap · 1 checked · 0 broken

All checked URLs in sitemap return 200. Crawl budget intact.

Technical health — robots, security headers, language — security headers 1/5 · robots ok · lang set
CheckStateWhy it matters
robots.txt existsWithout it, crawlers guess. With it, you control crawl + declare sitemap.
robots blocks everythingnoDisallow: / on User-agent: * = your whole site is blocked from indexing. Catastrophic if accidental.
robots declares sitemapSitemap: line in robots.txt is how crawlers without prior knowledge find your sitemap.
HSTS headerStrict-Transport-Security — forces HTTPS, minor ranking + trust signal.
X-Content-Type-OptionsPrevents MIME-sniffing attacks; part of security-score signals.
Content-Security-PolicyDefense-in-depth; not a direct ranking factor but part of site-quality signals.
X-Frame-OptionsClickjacking protection.
<html lang> attributeTells search + AI engines your content language. Missing = ambiguous targeting.
UTF-8 charset declaredPrevents character-encoding garble in SERP snippets.
Image SEO — alt text + lazy-load audit — 0 images · 0 missing alt · 0 lazy-loaded
MetricCountWhy it matters
Total <img> tags0Each is a potential discovery surface via Google Images.
With descriptive alt0Properly alt-tagged = indexed in image search + accessibility compliant.
Empty alt=""0Empty alt is correct ONLY for decorative images. Otherwise it kills image-search visibility.
Missing alt attribute entirely0Worst case — invisible to search + breaks accessibility. Fix: add alt="[descriptive text]" to every <img>.
lazy-loaded0loading="lazy" improves LCP. Below-fold images should have it; above-fold should not.
sameAs link verification — does every Wikidata/OpenLibrary/etc URL in your schema actually resolve? — 20 URLs checked · 4 broken

Broken sameAs URLs in schema = Google distrusts your knowledge-graph claims. Fix each one or remove from schema.

sameAs URLHTTP
https://www.wikidata.org/wiki/Q139182557200
https://openlibrary.org/authors/OL3714334A0
https://www.amazon.com/author/davidalyons405
https://www.goodreads.com/author/show/56310972.David_A_Lyons200
https://www.instagram.com/the_house_of_lyons/429
https://www.youtube.com/@DavidALyons200
https://substack.com/@davidalyonsauthor200
https://www.wikidata.org/wiki/Q139311193200
https://www.wikidata.org/wiki/Q139311362200
https://www.wikidata.org/wiki/Q139185676200
https://openlibrary.org/works/OL45366980W200
https://www.wikidata.org/wiki/Q139311652200
https://openlibrary.org/works/OL45371292W200
https://www.wikidata.org/wiki/Q139312285200
https://openlibrary.org/works/OL45371294W200
https://davidalyons.com/200
https://vehementlyinked.com/200
https://syncdtrilogy.com/200
https://vehementlyinked.substack.com/200
https://books.apple.com/us/author/david-a-lyons/id6744961715404
AI Mode / AI Overviews — appearance + readiness — 0 AI-overview impressions · 0 clicks · readiness 3/6

What this is: Google launched AI Overviews / AI Mode in Search Console as a new "search appearance" type. When Google's SGE cites your URL in an AI-generated answer, that impression shows up here under an AI-flagged appearance value. Below: the raw breakdown by every searchAppearance type GSC returned, plus a per-site audit of whether your homepage is structured the way AI Overviews picks pages from.

How to use it: If "AI overview impressions" is 0, Google has never cited you in an AI answer yet. Fix the readiness checks below and the HIGH/MED AI plan items — they are the on-page signals Google's SGE looks for. Once readiness reaches 5-6/6 and you ship FAQ schema + H2 questions, AI Overview impressions typically start appearing in 4-8 weeks.

Search appearance breakdown

GSC returned no search-appearance breakdown for this site yet.

AI-readiness audit

SignalStateWhy it matters for AI Mode
FAQPage schema✓ presentAI Overviews preferentially extracts from FAQPage Q&A pairs.
Article schema✗ missingAI Mode cites Article-schema pages with author+datePublished as authoritative.
HowTo schema✗ missingHowTo = direct-answer for procedural queries.
QAPage schema✓ presentQAPage = explicit question-answer format AI engines parse.
Speakable markup✗ missingMarks passages voice-AI surfaces read aloud.
Author byline✓ presentE-E-A-T signal AI engines weight higher.
datePublished✓ presentFreshness signal — without it content reads as undated.
dateModified✗ missingLast-updated date — affects whether AI engines pull from you vs newer sources.
<h2> questions on page0AI engines scan H2 questions as direct-answer candidates. Target 3-8.

How to actually get cited in AI Mode (specific steps)

  1. Add FAQPage schema with 5-8 Q&A pairs — highest-leverage AI Overview signal. Questions like "What is SYNCD about?", "Who is David A. Lyons?", "What order should I read the SYNCD trilogy in?", "What genre is SYNCD?", "Where can I buy SYNCD?"
  2. Wrap evergreen pages in Article schema with author (linking to David A. Lyons Person Wikidata Q-ID once created), datePublished, dateModified in ISO 8601 format.
  3. Make sure llms.txt is current — AI engines fetch it before answering. Auto-regen queued.
  4. Apply to Search Console Insights / AI Mode beta at search.google.com/search-console/insights — Google rolls out the dedicated AI Mode performance report by waitlist. Beta access just shows the data sooner; on-page work above doesn't require it.
  5. Apply to Google Discover via Publisher Center — Discover and AI Mode share signals (Article schema, dates, authorship). Approved Discover sources weight higher in AI Overviews.
Google's view of your homepage (URL Inspection API) — verdict: PASS · last crawl: 2026-05-26 · 1 rich results detected
SignalGoogle's answer
Indexing verdictPASS
Coverage stateSubmitted and indexed
Indexing stateINDEXING_ALLOWED
Last crawl by Google2026-05-26T11:38:46Z
Page fetch stateSUCCESSFUL
robots.txt stateALLOWED
You declared canonicalhttps://syncdtrilogy.com/
Google picked canonicalhttps://syncdtrilogy.com/ match
Mobile usabilityVERDICT_UNSPECIFIED
Rich results detected1 types
Core Web Vitals & PageSpeed — mobile perf: /100 · LCP - · CLS -
ScoreMobileDesktop
Performance/100/100
SEO (Lighthouse)/100/100
Accessibility/100-

Core Web Vitals (mobile)

MetricValueThreshold
LCP (Largest Contentful Paint)-< 2.5s
CLS (Cumulative Layout Shift)-< 0.1
FCP (First Contentful Paint)-< 1.8s
TBT (Total Blocking Time)-< 200ms
INP (Interaction to Next Paint)-< 200ms

Full report: pagespeed.web.dev

Identity collisions — queries that are NOT about you — 1 shown · 2 impr / 0 clicks wasted on wrong-person searches

What this is: Google shows YOUR URL for searches about other Davids, other Vehemently Inkeds, other SYNCDs. Each row is impressions you "earned" but for the wrong reason — they don't convert and they pollute your real ranking signal.

How to fix the underlying problem: You can't fix individual queries — these are downstream of the bigger disambiguation issue. The root fixes: 1) Build the Person Q-ID for David A. Lyons in Wikidata (see Wikidata section above) so AI engines have a distinct node. 2) Add Person+Organization schema with sameAs Wikidata + OpenLibrary URLs on every site (auto-fix queued). 3) Build inbound brand-anchor links so your site is the strongest "David A. Lyons author" signal in Google's graph. 4) Track this list weekly — when collision impressions drop, your disambiguation is working.

Query (not yours)ImprClkPosWhy it is not yours
sync d2066no brand marker (Lyons/SYNCD/VI) — likely about someone else
Plan to rank up — 10 actions · 5 HIGH · 1 AUTO · 9 need you

Each row tells you the action, why it matters in your specific situation, the exact steps to do it, and whether the routine will handle it automatically or you have to.

HIGH
Strengthen syncd (currently buried at position 48)
NEEDS YOU
Why this matters for you: Other sites outrank you on YOUR OWN brand term. This is the disambiguation problem.
Steps: 1) Edit homepage title to put syncd at the very start. 2) Add the term in the first H1 + first sentence. 3) Build Wikidata Person/Org entity (see Wikidata section below) so AI engines have a separate node for you. 4) Get one external citation per month for 3 months. 5) Recrawl will be triggered by daily IndexNow ping.
HIGH
Own brand term syncd trilogy
NEEDS YOU
Why this matters for you: You don't rank at all for it. The page exists but Google has no signal linking this term to your URL.
Steps: 1) Edit your homepage. 2) Open Yoast SEO panel. 3) Set SEO Title to start with syncd trilogy followed by your current title. 4) Add the term verbatim in the first H1 and first paragraph. 5) In schema, add a WebSite block with name=syncd trilogy. 6) From your two sister sites, add one inline link with anchor text syncd trilogy. 7) Save and wait 2-4 weeks for Google to recrawl + re-rank.
HIGH
Own brand term cryptoamnesia
NEEDS YOU
Why this matters for you: You don't rank at all for it. The page exists but Google has no signal linking this term to your URL.
Steps: 1) Edit your homepage. 2) Open Yoast SEO panel. 3) Set SEO Title to start with cryptoamnesia followed by your current title. 4) Add the term verbatim in the first H1 and first paragraph. 5) In schema, add a WebSite block with name=cryptoamnesia. 6) From your two sister sites, add one inline link with anchor text cryptoamnesia. 7) Save and wait 2-4 weeks for Google to recrawl + re-rank.
HIGH
Own brand term cryptoanomaly
NEEDS YOU
Why this matters for you: You don't rank at all for it. The page exists but Google has no signal linking this term to your URL.
Steps: 1) Edit your homepage. 2) Open Yoast SEO panel. 3) Set SEO Title to start with cryptoanomaly followed by your current title. 4) Add the term verbatim in the first H1 and first paragraph. 5) In schema, add a WebSite block with name=cryptoanomaly. 6) From your two sister sites, add one inline link with anchor text cryptoanomaly. 7) Save and wait 2-4 weeks for Google to recrawl + re-rank.
HIGH
Own brand term cryptogenesis
NEEDS YOU
Why this matters for you: You don't rank at all for it. The page exists but Google has no signal linking this term to your URL.
Steps: 1) Edit your homepage. 2) Open Yoast SEO panel. 3) Set SEO Title to start with cryptogenesis followed by your current title. 4) Add the term verbatim in the first H1 and first paragraph. 5) In schema, add a WebSite block with name=cryptogenesis. 6) From your two sister sites, add one inline link with anchor text cryptogenesis. 7) Save and wait 2-4 weeks for Google to recrawl + re-rank.
MED
Add cold-discovery content
NEEDS YOU
Why this matters for you: 100% of your impressions are from people who already typed your name. Zero cold discovery — no one is finding you by typing a topic that interests them.
Steps: 1) Pick 3 topics adjacent to your work (e.g. "ergodic fiction", "House of Leaves successor", "AI-as-narrator novels", "Tulsa literary press"). 2) For each, write a 1000-word post on your blog/Substack covering it. 3) Cross-link to your books from within each post. 4) Submit each post URL via IndexNow (the daily routine will pick them up if added to sitemap). 5) Expect first impressions in 2-3 weeks.
MED
Add Article schema to evergreen pages
NEEDS YOU
Why this matters for you: AI Overviews cites Article-schema pages with author + datePublished + dateModified as authoritative sources. Without Article schema, your pages compete in the un-attributed bucket.
Steps: 1) For each substantial page (about, book pages, essays), wrap content in Article JSON-LD with: headline, author (@id linking to David Person entity), datePublished, dateModified, publisher (@id linking to VI Org). 2) Use ISO 8601 dates. 3) Cite source URLs where claims have sources. 4) Recrawl via IndexNow.
MED
Add 3-5 <h2> questions to homepage
NEEDS YOU
Why this matters for you: AI engines scan H2 questions as candidate prompts to answer. Pages with <h2>What is X?</h2> structure get parsed as direct-answer sources.
Steps: 1) Add an "FAQ" section to your homepage. 2) Use <h2> for each question (questions readers actually ask). 3) Follow each <h2> with a 40-60 word <p> that directly answers it. 4) Same Q&A pairs feed the FAQPage schema (HIGH priority above).
MED
Mobile usability verdict: VERDICT_UNSPECIFIED.
NEEDS YOU
Why this matters for you: Mobile-first index — non-mobile-friendly pages get downranked across all devices.
LOW
Add speakable schema marker
AUTO (daily)
Why this matters for you: Speakable schema tells Google Assistant + voice-AI surfaces which parts of your page to read aloud. Direct signal for voice-answer inclusion.
AUTO: tomorrow's run will add SpeakableSpecification to the WebSite schema pointing at your main hook paragraph.

How this report proves changes work

index: /home/u998779868/domains/syncdtrilogy.org/public_html/index.html · fix log: /home/u998779868/geo_seo_routine/fixes.jsonl · history: /home/u998779868/geo_seo_routine/history.jsonl · IndexNow key: f78d33a114e5939063e644b30e0ea0ba