Tags
25 posts
An explanation of the roles of SEO and web accessibility in how AI search finds documents and generates answers. Using a hypothetical pricing page, this article examines how to verify retrieval paths and information accuracy, and how to apply checklists and LLM review to CMS operations.
I counted every word in Google's AI features doc: zero hits for opt out, opt-out, or exclude. Why no AI-only exclusion lever exists, and what to do instead.
incidents.json gives the August 2026 spam update a minute-level UTC start. Search Console's join key is a PT date. The join leaves a mixed boundary day.
Platform properties went global on 2026-07-29. Search Console API docs still stop at 2024-07-23, so automated dashboards see Instagram, TikTok, X, YouTube last.
Ten of 33 robots.txt cells let a blocked URL through and Codex clipped the back of a 34 KiB AGENTS.md. All 219 runs exited 0. Which parser gave your verdict?
I built 69 text-fragment links from my own production build and clicked each one in Chromium. All 48 prose quotes landed; 14 of 15 code-block quotes did not.
A post untouched since October reports Last-Modified as yesterday. Its ETag is just file mtime and size in hex, so one deploy voids every 304 you could earn.
Six title channels agreed across 1,296 pages. The seventh, inbound anchor text, matched the target heading on 0.7% of 18,296 links. One wrapper caused it.
Across 1,334 pages, 24,948 of 46,382 internal links pointed at a slash-less URL that 301-redirects. The root cause, a four-stage fix, and the audit that hit zero.
A breadth-first crawl of 1,330 built pages put 1,276 posts at depth 2. Dropping the four flat archives left 296 of them unreachable from the homepage.
Google retired FAQ rich results on May 7, 2026. FAQPage JSON-LD still passes the schema validator but returns DEPRECATED. What to change in code and content.
I added Restaurant structured data to my restaurant-discovery PWA, then fed the same three defects to three validation layers to measure which one catches what.
A stray nosnippet no longer hides your snippet only. Google says it blocks the page as AI Overview input. I built broken and fixed pages and a parser to audit.
A JSON-LD parser passes markup no search engine can read: schema.org sets @vocab, so typos and wrong casing expand into valid JSON-LD. A 60-line schema-aware validator catches them in CI, with real logs.
The same Product entity in three syntaxes, bytes and fragility measured. Google treats them equally, so the reason to choose JSON-LD is coupling, not ranking.
GPTBot and ClaudeBot don't render JS. Here's a curl experiment proving client-side pages are invisible to AI search, plus how to fix it server-side.
Ship priority 1.0 with changefreq always and Google drops both. The only field it uses is lastmod, and only when verifiably accurate. I ran three sitemaps through the official XSD to see what really counts.
My JSON-LD validated as three disconnected islands. Here's how @id references stitch Organization, WebSite, and Article into one @graph, measured with jsonld.
I aimed a 30-line checker at my build output: 248 posts passed their hreflang clusters, the homepage failed. Google's reciprocity rules, run logs, and the fix.
Many sites block GPTBot in one line and call it done. I built a robots.txt that separates training, search, and fetch crawlers, then verified it with a parser.
Inject LocalBusiness JSON-LD with JavaScript and the raw HTML has zero ld+json blocks. I compare it with server-side output, Google's stance and ranking limits.
A hands-on guide to diagnosing and fixing the technical issues behind AdSense rejections on a multilingual Astro blog—ads.txt conflicts, 996 ghost pages, and sitewide sitemap 404s.
Get content cited by ChatGPT and Perplexity with AEO. This Agent Effi Flow case study covers schema markup, FAQ optimization, and structured data design.
After Google AdSense rejected my site for "Low Value Content", I used ChatGPT, Claude, and Gemini to analyze the issues and improved approval probability from 5.5 to 8.5 out of 10. Here is my experience.
From SEO foundation to AEO strategy: real implementation case study with measurable results from the Agent Effi Flow project