iNevidimka.
a zine about getting found — issue 01
filed under: home / blog

Notes on getting found.

SEO & AI Search Blog

Written the way I build pages for clients — definitional, quotable, structured for both readers and LLMs. The blog is the demo.

Open the SEO Wiki
GEOWhat Is llms.txt? Format, Example and SEO RealityThe proposed Markdown index for LLMs, explained without treating it as a ranking factor.GEOGEO vs SEO: What Changes for AI SearchSame goal: being found. Different engine, different rules. A working comparison.AEOAEO vs SEO: Be the Answer, Not a FootnoteAEO is not the new SEO. It is the answer-shaped layer on top of it: clearer entities, cleaner answers, better evidence, and pages AI systems can confidently cite.GEOWhat Is Generative Engine Optimization (GEO)?A source-backed definition of GEO and a practical measurement framework.AEOWhat Is Answer Engine Optimization (AEO)?A practical definition of AEO, its limits and the work that can actually be validated.ToolsBest GEO Tools for AI Search Visibility in 2026What actually tracks AI citations today: and what is marketing noise.Tools10 Best Answer Engine Optimization (AEO) Tools in 2026Ten AEO platforms compared by engine coverage, prompt limits, citations, workflow and price.GEOHow to Rank in ChatGPT: 9 Steps for AI VisibilityA practical 9-step system for getting found and cited in ChatGPT.AEOHow to Show Up in Google AI OverviewsWhat Google documents about visibility in AI Overviews, plus a practical audit workflow.GEOHow to Optimize for PerplexityHow to improve Perplexity source eligibility without inventing a ranking formula.LinksLink building that survives AI searchLink building for durable editorial and business value, with AI citation effects measured separately.LocalLocal SEO for Dentists: GBP ChecklistA practical checklist for accurate GBP categories, policy-compliant reviews, useful treatment pages and consistent practice information.Technical SEORank Math SEO Titles: Dynamic VariablesSet SEO titles once with variables: not one post at a time.Technical SEOtarget="_blank": SEO and Security RulesNew-tab links: harmless for SEO, risky without rel=noopener.Technical SEOExclude yclid and ysclid from URLsTracking parameters that quietly spawn duplicate URLs: and how to tame them.Technical SEOScreaming Frog Response Time: What It MeansResponse Time isn't page speed: here's what it actually tells you.WordPressWordPress Valid JSON Response Error: FixesThe block-editor publishing error, diagnosed from the failed response instead of guessed fixes.SEONegative Keywords: Definition & List BuildingThe list that stops you paying for the wrong clicks.WordPressTable of Contents in WordPress: the SEO VersionBuild a useful WordPress TOC from a sound heading outline, then validate anchors, accessibility and performance.AnalyticsLost Analytics Access? Recovery PlaybookThe admin left and no one has access: here's the recovery order.On-page SEOHow many H1 tags per page? The honest answerGoogle tolerates multiple H1s. You should still ship one.AnalyticsGoogle Search Console Access: Safe User SetupOwner vs Full vs Restricted: grant the least access that does the job.Local SEOLocal SEO Checklist for Google Maps and AI Search in 2026The local SEO checks I use, with platform rules separated from industry observations.GEOGEO/AEO Tactics: What the Evidence Supports in 2026A practical AI-visibility playbook with the strength and limits of each source made explicit.GEOSemantic Triples for SEO: Subject, Predicate, ObjectA practical guide to semantic triples, RDF, entity relationships and their real role in SEO and AI search.SEOGoogle E-E-A-T (EEAT) SEO Checklist: 46-Point AuditA source-led 46-point checklist with applicability rules, evidence requirements, high-risk content controls and an honest scoring method.

Be the answer, not a footnote.

want a topic covered? suggest it
[email protected]+1 (352) 665-8350LinkedInTelegramGoogle Maps
iNevidimka — Dima MochalovPrivacy · Terms · Editorial · Methodology · © 2026
Operated by Mochalov Dmitri Andrei IE (Individual Entrepreneur (Armenia)) · Reg. 20268705 · Arghishti str. 7, suite 0015, Yerevan, Kentron, Armenia · +1 (352) 665-8350 · Google Maps. All engagements are governed by our Terms of Service.