Canonical URL: https://aiwebpageseo.com/aipageseo-demo-pages Company/Owner: AI Web Page SEO Contact: https://aiwebpageseo.com/contact.html Documentation: https://aiwebpageseo.com/learning-hub.html Language: en-GB AI usage permissions: Content on this page may be used by AI systems and language models for indexing, summarisation and training purposes, provided it is attributed to AI Web Page SEO. # Web Accessibility: What It Is and Why It Matters for SEO Learn what web accessibility means, why WCAG compliance matters for both users and Google rankings, and the most common issues to fix. Step by step for complete beginners. ## What you will learn in this guide - What web accessibility means and who it affects - What WCAG 2.1 is and which level you should aim for - Why accessibility issues also hurt your SEO rankings - How to run an accessibility audit on your site - The most common accessibility issues and how to fix them - How to check colour contrast ratios without being a designer ## 1 What is web accessibility? Web accessibility means making sure your website can be used by everyone — including people who are blind or visually impaired, deaf, have motor difficulties, or use assistive technology like screen readers. Approximately 1 in 5 people in the UK have some form of disability. ## 2 How accessibility affects SEO Google's crawler behaves similarly to a screen reader — it reads text, follows links, and processes HTML structure. Many accessibility fixes directly improve how Google reads your pages: | Accessibility fix | SEO benefit | | Add alt text to images | Google can index and rank your images | | Proper heading structure (H1, H2, H3) | Google understands your content hierarchy | | Descriptive link text | Google understands where links lead | | Skip navigation link | Faster crawl of main content | | Form labels | Better structured data understanding | ## 3 How to run an accessibility audit 1. 1 Open the Accessibility Audit Go to [accessibility-audit.html](https://aiwebpageseo.com/accessibility-audit.html) and enter the URL of a page you want to audit. 2. 2 Review Level A violations first Level A issues are the most critical — these are failures that completely block some users from using your page. Fix these before anything else. 3. 3 Check contrast ratios Text must have a contrast ratio of at least 4.5:1 against its background for normal text, and 3:1 for large text. The tool shows the exact ratio for any failing elements. 4. 4 Fix missing alt text on images Every image that conveys information needs an alt attribute describing what it shows. Decorative images should have `alt=""` — an empty alt attribute — so screen readers skip them. ## 4 The most common accessibility issues 1. ⚠ Images without alt text Add `alt="description of image"` to every img tag. For example: `` 2. ⚠ Form inputs without labels Every input needs a label. Add `Email address` before each input, with a matching `id` on the input itself. 3. ⚠ Low colour contrast Grey text on a white background often fails. Use a contrast checker or the Accessibility Audit tool to find failing elements, then darken the text colour until it passes. Accessibility is the SEO improvement most site owners skip — which means it is also an opportunity. Sites that fix accessibility issues often see ranking improvements because many accessibility fixes are the same things Google looks for. And fixing them is the right thing to do for your users. Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # AEO: How to Make Your Site Visible to AI Search Engines Learn what AEO (Answer Engine Optimisation) is, why AI chatbots like ChatGPT and Perplexity may not be citing your site, and how to fix it. Step by step for complete beginners. ## What you will learn in this guide - What AEO is and how it differs from traditional SEO - Why AI chatbots may be ignoring your website - What llms.txt is and why you need one - How structured data helps AI understand your content - How to audit your AI search visibility - The quickest fixes to improve your AI citation rate ## 1 What is AEO? AEO stands for Answer Engine Optimisation. While traditional SEO focuses on ranking in Google's blue link results, AEO focuses on being cited by AI tools like ChatGPT, Perplexity, Google AI Overviews and Claude when they answer questions. ## 2 Why AI tools might be ignoring your site AI crawlers are different from Googlebot. They may be blocked by your robots.txt, unable to read your content, or simply not find your pages authoritative enough to cite. Common reasons: | Issue | Effect | | AI bots blocked in robots.txt | ChatGPT, Perplexity etc cannot crawl your site | | No llms.txt file | AI tools have no guide to your most important content | | No FAQ or HowTo schema | AI cannot identify question-answer content on your pages | | Thin or vague content | AI tools prefer direct, specific answers to questions | | No author information | E-E-A-T signals are weak — AI prefers expert sources | ## 3 What is llms.txt? llms.txt is a file you put at the root of your website (like robots.txt) that tells AI language models what your site is about, which pages are most important, and how to understand your content. It is the AI equivalent of a sitemap. ## 4 How to improve your AEO score 1. 1Run the AEO CheckerGo to [content-tools.html#aeo](https://aiwebpageseo.com/content-tools.html#aeo) and enter your page URL. The tool checks bot access, structured data, FAQ schema and generates your llms.txt. 2. 2Allow AI bots in robots.txtCheck your robots.txt does not block GPTBot, PerplexityBot, ClaudeBot or Google-Extended. If it does, remove those disallow rules. 3. 3Add FAQ schema to your key pagesAdd FAQPage schema markup to pages that answer common questions. This directly signals to AI tools which questions your page addresses. 4. 4Deploy your llms.txt fileUpload the generated llms.txt to your server root. Verify it is accessible at https://yoursite.com/llms.txt AEO is the fastest moving area of SEO right now. The rules are still being written. But the fundamentals are clear — allow AI bots to crawl your site, give them clear structured data to read, and create content that directly answers the questions your customers are asking. Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # AI Agent Compatibility: Letting ChatGPT and Claude Use Your Site Learn how AI agents like ChatGPT Operator and Claude Computer Use interact with websites, and how to make your forms, buttons and navigation agent-friendly. ## What you will learn in this guide - What AI agents are and how they differ from search crawlers - Why generic crawler signals don't apply to agents - How to make forms agent-fillable - Why "Click here" buttons fail for agents - How llms.txt and accessibility overlap with agent compatibility ## 1 What is an AI agent? An AI agent is an LLM-powered system that browses websites on behalf of a user — clicking links, filling forms, and completing tasks. Examples: ChatGPT Operator, Claude Computer Use, Anthropic Computer-Using Agent, Perplexity Auto. ## 2 How agents differ from crawlers | Crawler | Agent | | Reads HTML once | Interacts continuously | | Doesn't click buttons | Clicks every button on the path to a task | | Ignores forms | Must fill forms to complete tasks | | Stateless | Maintains session and context | | Cares about robots.txt for indexing | Cares about robots.txt for permission to act | ## 3 How to make your site agent-friendly 1. 1Add autocomplete attributes to every form fieldAgents use autocomplete tokens to know what each field expects. `autocomplete="email"`, `autocomplete="name"`, `autocomplete="tel"` etc. 2. 2Use real `` elementsNot just placeholder text. `Email` with matching id on the input. Agents read labels to understand fields. 3. 3Replace "Click here" with descriptive button textBad: "Click here". Good: "Add to basket", "Submit booking", "Continue to checkout". Agents predict what a button does based on its text. 4. 4Ensure every key action is reachable by keyboardTest with Tab and Enter. If you can't complete a task with just the keyboard, an agent often can't either. ## 4 AI crawler robots.txt directives Decide which AI agents you allow. Add to your robots.txt: ## 5 Before anything else: check your logs Every recommendation in this guide is worthless if agents cannot reach your origin, and there is exactly one place where that fact is recorded: your access log. Filter it for the agent user-agents — ChatGPT-User, ClaudeBot, PerplexityBot, OAI-SearchBot, Googlebot — and look at two things. Are they arriving at all? And what status code are they getting? The answer is frequently a surprise. Sometimes the traffic is negligible, and the honest conclusion is that this whole topic is premature for your site and your effort belongs elsewhere. Far more often, the agents are arriving and being served 403s by a bot-mitigation rule that somebody enabled by default years ago and nobody has looked at since. ## 6 Training and retrieval are different decisions The robots.txt block above allows ChatGPT-User, ClaudeBot, PerplexityBot and OAI-SearchBot. It is worth understanding what each of those directives actually controls, because the agents are not interchangeable and the most common configuration mistake follows from treating them as though they were. | Agent | What it does | Blocking it means | | GPTBot | OpenAI training crawler | Your content is not used to train models. It does **not** remove you from ChatGPT's answers. | | OAI-SearchBot | Fetches pages for ChatGPT's search | You are not retrieved as a source for live answers. This is the one that costs you citations. | | ChatGPT-User | Fetches a page a user asked about | ChatGPT cannot open your page when a user asks it to. | | Google-Extended | Gemini training only | No effect on Google Search, on rankings, or on AI Overviews. | The pattern to avoid: a site blocks GPTBot to opt out of training, feels it has taken a position, and is then surprised to still be quoted by ChatGPT. Or the reverse — a site blocks everything with "GPT" or "AI" in the name and quietly removes itself from every assistant's citations, having intended only to decline training. ## 7 Put the substance in the served HTML Agents divide into two kinds and the distinction decides how much of your site they can see. Browser-driving agents genuinely run a browser: they wait for scripts, they see the rendered page, they can click. Retrieval-oriented fetchers generally take the HTML as it arrives from your server and parse it — no rendering, no waiting, no JavaScript. For that second group, anything your page assembles client-side after load does not exist. Not "ranks lower" — does not exist. Prices fetched from an API on mount. Availability rendered by a framework after hydration. FAQ answers inside an accordion that only populates on click. Product specifications in a tab that loads its content when the tab is selected. You can check this in ten seconds without any tooling: view the page source, or fetch the URL with curl, and search for the text you care about. If your price is not in that response, the fetchers cannot see your price. It does not matter how perfect it looks in a browser. The fix is server-side rendering, or static generation, or simply putting the important content in the initial HTML and enhancing it afterwards. It costs nothing, it helps search engines and assistants alike, and it makes the question of what each agent supports irrelevant. ## 8 Agent compatibility is accessibility with a new name Read back through the practical advice in this guide — real label elements, autocomplete tokens, buttons that are buttons, meaningful link text, content present in the markup rather than conjured by script — and notice what it amounts to. It is the accessibility checklist. Almost line for line. That is not a coincidence. A screen reader and an agent face the same problem: they must understand a page without seeing it. Both need the structure to carry the meaning, because neither can infer from a layout that a bold blue rectangle is the submit button, or that the text floating above a box is its label. 1. 1A placeholder is not a labelIt disappears on focus, it fails contrast requirements, and it gives a machine nothing to bind the field to. Use a real with a matching id. 2. 2A div with a click handler is not a buttonIt cannot be focused, cannot be activated by keyboard, and announces nothing. Use . Every agent, every screen reader and every keyboard user benefits immediately. 3. 3"Click here" is not link textLink text is a description of the destination. It is what a machine uses to understand what it is about to open, and what a screen-reader user hears in a list of links stripped of context. 4. 4Errors must be in the markupA validation failure shown only as a fading toast is invisible to anything that is not watching the screen. Render it in the DOM, associated with the field it concerns. The encouraging consequence: this work was already worth doing, it is legally required in many jurisdictions, and it has a constituency of real human beings who benefit from it today. Agent compatibility is a second reason to do something you should be doing anyway — not a new discipline requiring new tooling, and certainly not a special interface built alongside your real one. ## 9 Frequently asked questions Check rather than assume, because the answer varies enormously by site and the only place it is recorded is your own access log. Filter for the agent user-agents — ChatGPT-User, ClaudeBot, PerplexityBot, OAI-SearchBot and the rest — and look at both the volume and the status codes they receive. What you find is frequently a surprise in one of two directions: either the traffic is negligible and the whole topic is premature for your site, or the agents are being served 403s by a bot-mitigation rule nobody remembers configuring. Neither of those is visible from anywhere except the log. This is the single most common cause of an invisible site, and it produces no error anybody notices. Bot-mitigation rules — at Cloudflare, at your CDN, in a security plugin — frequently match on unfamiliar user-agent strings or on request patterns that look automated, and they were usually enabled by default rather than by decision. The result is a permissive robots.txt sitting in front of an origin that silently refuses every agent request. robots.txt is a request to well-behaved clients; the WAF is what actually decides who gets a response. Only the access log tells you which one is winning. Some do and some do not, and building on the assumption that they all do is the expensive mistake. Browser-driving agents genuinely operate a browser, so they see what a user sees after scripts run. Retrieval-oriented fetchers generally take the HTML as served and parse it, which means anything assembled client-side after load simply does not exist for them — your prices, your availability, your FAQ answers, your product specifications. The safe rule is to put the substance in the served HTML. It costs nothing, it helps every client including search engines, and it removes the question entirely. The same things a screen reader needs, which is the useful insight here: agent compatibility and accessibility are very nearly the same discipline. A real label element associated with its input, so the field has a name rather than a placeholder that vanishes on focus. An autocomplete token, so the agent knows this field wants an email and that one a postcode. A submit button that is a button, not a div with a click handler. Error messages rendered in the markup rather than only in a toast that disappears. A form that a blind user can complete is a form an agent can complete. No — and the sites that have tried have mostly ended up maintaining two things and getting neither right. There is no agent-specific protocol you need to adopt, no schema type that admits you, and no file that grants you agent compatibility. What agents need is a site whose structure honestly reflects its content: semantic HTML, real form controls, meaningful link text, substance in the served markup, and accurate structured data where it disambiguates something. That is the same list you would write for accessibility, and doing it once serves everybody. No, and this confusion costs sites real visibility. GPTBot is OpenAI's training crawler; blocking it removes your content from a training corpus. The agents that fetch pages to answer a live user's question are different — OAI-SearchBot and ChatGPT-User — and they are governed by their own directives. A site that blocks GPTBot to opt out of training, believing it has done nothing else, has done nothing else. A site that blocks all three has removed itself from ChatGPT's cited answers, and usually did not intend to. Decide about training and about retrieval separately, because they are separate decisions. Google-Extended controls whether your content is used for Gemini model training. It has no effect whatsoever on Google Search, on your rankings, or on whether you appear in AI Overviews — those run on ordinary Googlebot access and ordinary Search eligibility. Sites disallow Google-Extended believing they are opting out of AI Overviews and are then puzzled to find themselves still appearing in them; sites also avoid disallowing it for fear of harming their rankings, which is equally unfounded. It does one narrow thing, and that thing is training. Agent compatibility is the next decade's SEO. Sites that are usable by both humans and AI agents will capture a growing share of conversions. The fixes overlap heavily with accessibility — making your site agent-friendly usually makes it human-friendly too. Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # AI Agent Readiness: How to Make Your Site Visible to AI Agents Most websites were built for human visitors and search engine crawlers. But a new kind of visitor is growing fast — AI agents. These are automated systems that browse, read and interact with websites on behalf of users. If your site is not set up to welcome them, you are invisible to the next generation of web infrastructure. ## What is AI Agent Readiness? AI Agent Readiness means your website publishes the right signals and files that AI agents, crawlers and automated tools need to discover, understand and interact with your site. Think of it like having a proper sign on your shop door — without it, automated systems pass you by. ## Why does it matter? AI agents are increasingly being used to find information, book services, compare products and complete tasks online. It is worth being honest about the evidence here: no assistant operator publishes its retrieval logic, and there is no demonstrated relationship between publishing discovery files and being cited. What is demonstrable is the opposite failure — a site that agents cannot fetch at all cannot be cited by anything, and that is a real and common problem. Treat the files below as cheap hygiene, and treat crawler access as the thing that actually matters. ## The 4 areas you need to fix ## What to do next - Run the free AI Agent Readiness audit on your domain - Create `/llms.txt` at your root — see llmstxt.org for the spec - Add `Content-Signal: ai-train=no, search=yes, ai-input=no` to your robots.txt - Allow GPTBot, ClaudeBot, PerplexityBot and Google-Extended in robots.txt - Create your `/.well-known/` discovery files - Add a Link header pointing to your llms.txt ## Start with the log, not the checklist Everything on the four-area list above is cheap, and none of it matters if agents cannot reach your origin in the first place. There is exactly one place where that fact is recorded, and it is not your robots.txt. It is your access log. Filter it for ClaudeBot, OAI-SearchBot, ChatGPT-User, PerplexityBot and Googlebot. Look at two things: are they arriving, and what status code are they getting? A very large number of sites discover at this point that a bot-mitigation rule — at Cloudflare, at their CDN, in a security plugin somebody installed years ago — has been returning 403 to every agent request for months. The robots.txt was permissive the entire time. ## What the evidence actually supports The AI-readiness field is full of confident claims, and it is worth separating the ones that stand up from the ones that do not — because the effort is finite and most of it is currently being spent in the wrong place. **Unproven.** That llms.txt raises citation rates. That security headers act as trust signals to AI systems. That denser structured data wins citations. That any file or score improves your standing with an assistant. No operator publishes retrieval logic, so nobody outside those companies is in a position to make these claims, and the ones being made are not supported by anything. **Demonstrable.** That an agent which receives a 403 cannot cite you. That a retrieval fetcher which parses rather than renders cannot see content your JavaScript assembles after load. That a page containing no self-contained answer offers nothing quotable. These are mechanical facts about how the systems work, and each is checkable on your own site this afternoon. The practical consequence: publish the files, because they cost an hour and do no harm. Then spend the remaining effort on the three things that are actually load-bearing, rather than on optimising a score. ## Training and retrieval are separate decisions The advice to allow GPTBot, ClaudeBot, PerplexityBot and Google-Extended treats four quite different directives as one. They are not interchangeable, and conflating them is how sites accidentally remove themselves from assistants they wanted to appear in. - **GPTBot** — OpenAI's training crawler. Blocking it keeps your content out of a training corpus. It does *not* remove you from ChatGPT's answers. - **OAI-SearchBot and ChatGPT-User** — these fetch pages to answer a live user's question. Blocking these is what costs you citations in ChatGPT. - **Google-Extended** — Gemini training only. It has no effect on Google Search, on rankings, or on whether you appear in AI Overviews, which run on ordinary Googlebot access. - **ClaudeBot and PerplexityBot** — the fetchers for those assistants. Same logic: allow them if you want to be citable there. Answer the two questions separately. Do you want your content used to train models? Do you want to be citable when somebody asks an assistant something your pages answer? Many sites answer no and yes, which is entirely coherent — but it requires naming the agents individually rather than reaching for a rule that matches anything with "GPT" or "AI" in the string. ## The one thing no file can do for you Suppose you complete every check. The files are published, the headers are set, the crawlers are allowed and your access log confirms they are arriving and receiving 200s. What then decides whether an assistant cites you? What is on the page. These systems surface passages that answer a question and hold up when lifted out of context — and most marketing pages contain no such passages. They contain persuasion, which depends on the layout, the imagery, and a reader who already wants to believe. Extract a paragraph of it and read it cold, and it says nothing. So the test worth applying to every important page: take a paragraph out, read it as somebody who has never seen your site, and ask whether it answers a real question completely. If it does not, no discovery file will save it. If it does, you have written the only thing on this entire list that a machine can actually use — and you have done it in a way that serves the human reader identically, which is why it is the one recommendation here that cannot become obsolete when the fashion changes. ## Frequently asked questions ### 🛰️ Check your AI Agent Readiness score Run a free audit on your domain. See which of the 16 checks you pass and get specific fix instructions for any that fail. ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # AI-Aware Schema: Structured Data for AI Citations Learn which JSON-LD fields specifically help AI engines like ChatGPT, Claude and Perplexity cite your content accurately, and how to add the entity references that prevent hallucination. ## What you will learn in this guide - Why AI engines need different schema signals than Google - The role of @id and entity disambiguation - Person schema for authors with knowsAbout signals - How to wire dateModified to real edit timestamps - Why sameAs links matter more for AI than for SEO ## 1 Why AI needs schema differently Google can extract meaning from messy HTML when it has to. AI engines benefit much more from clean structured data because they need to reason about entities, dates, and authority — not just match keywords. ## 2 Entity @id references Every entity in your schema (Person, Organization, Product) should have a unique @id URL. This is how AI engines link the same entity across pages. When this same Jane is referenced from multiple articles, use the @id as a reference: `"author": {"@id": "https://yoursite.com/team/jane-smith#person"}`. The full Person object goes once on the author page; references go everywhere else. ## 3 Critical AI-aware fields | Field | Why AI cares | | author (Person object, not string) | Disambiguates which expert wrote the content | | datePublished + dateModified | AI weights recent content higher; stale timestamps hurt citations | | knowsAbout (on Person) | Tells AI which topics this author is authoritative on | | sameAs (on Person/Organization) | LinkedIn, Twitter, Wikipedia links establish identity across web | | mainEntity / mainEntityOfPage | Tells AI what this page is primarily about | | inLanguage | Avoids cross-language citation confusion | ## 4 How to audit your AI schema 1. 1Run the AI Schema AuditOpen [schema-tools.html#ai-schema](/schema-tools.html#ai-schema). The tool scores each page on AI-aware fields, not just Google rich-result requirements. 2. 2Find hallucination risksThe tool flags ambiguous entity references: string-only authors, missing Person @id, stale dateModified. Each is a potential AI citation error. 3. 3Fix authors firstMost sites lose AI visibility because authors are strings. Convert top 10 authors to full Person objects with @id, knowsAbout, sameAs links to LinkedIn and other authoritative profiles. 4. 4Wire real datesdateModified should be the actual last meaningful edit, not the deploy date. Most CMSs have a "last revised" field — use it as the source. AI-aware schema is regular schema with stricter entity discipline. The same JSON-LD that helps Google also helps ChatGPT and Claude — but only if you take the time to use stable @id references and complete Person/Organization objects. Most sites are still using string-only authors, which is the biggest single AI visibility gap. Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # AI Visibility: Tracking Your Citations in ChatGPT, Claude and Perplexity Learn what AI visibility is, why it differs from regular SEO, and how to track whether ChatGPT, Claude, Perplexity and Gemini mention your site in their answers. ## What you will learn in this guide - What AI visibility is and how it relates to SEO - The three types of AI prompts you should track - Why citation rate matters more than ranking - How to track your share-of-voice vs competitors - What to do when AI engines cite outdated info about you ## 1 What is AI visibility? AI visibility is the rate at which AI search engines and chatbots mention or cite your website when answering relevant questions. Unlike Google rankings, there is no public position list — the only way to measure is to ask the AI engines themselves. ## 2 The three prompt types to track | Prompt type | Example | Why track | | Branded | "What is [your brand]?" | Easy to win; confirms factual accuracy of AI knowledge | | Category | "Best project management software" | The discovery battleground — captures buyers in research mode | | Problem | "How do I run async standups?" | Earliest stage of the funnel — hardest but most valuable | ## 3 How to track AI visibility 1. 1Define 20-50 promptsMix all three types. Cover branded prompts, your top 10 category queries, and 5-10 problem statements your product solves. 2. 2Run them weekly across enginesManually or via the AI Visibility Tracker, ask each prompt in ChatGPT, Claude, Perplexity and Gemini. Note whether your site is cited. 3. 3Calculate citation rateCitations / total prompts × 100. A 30-50% rate on category prompts is strong; under 10% means you have an AI visibility problem. 4. 4Track competitorsRun the same prompts asking about competitors. If their citation rate is climbing while yours stays flat, you are losing AI share-of-voice. ## 4 How to improve AI visibility AI visibility is driven by signals slightly different from Google rankings: | Signal | Importance for AI | | Mentions on high-authority sites | Very high — wikipedia, news, trade pubs are heavily weighted | | Structured data (JSON-LD) | High — Person, Organization, Product schemas with @id | | llms.txt file | Medium — helps AI engines discover key pages | | Backlinks | Medium-high — overlaps with Google but weighted differently | | Content depth | High — AI engines favour comprehensive answers over short pages | | Freshness signals | Medium — dateModified, dateline schema all matter | AI visibility is the new frontier of SEO. The metrics are different, the playbook is partially different, but the principle is the same: be the most authoritative, well-cited source on a topic and AI engines will mention you. Start with branded prompts, then expand to category and problem prompts. Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # Algorithm Impact: Figuring Out Whether a Google Update Hit You Learn how to tell whether a sudden traffic drop is from a Google algorithm update, what each major update type tends to penalise, and what the realistic recovery options look like. ## What you will learn in this guide - How to tell algorithm hit from technical issue from seasonality - Major Google update types and what each targets - How to use category volatility (the Sensor index) to confirm - Realistic recovery timelines for each update type - When to fight back vs when to wait ## 1 Is it an algorithm hit? Three things can cause a sudden traffic drop: | Cause | Signal | Action | | Algorithm update | Drop coincides with Google update; affects multiple sites in your category | Diagnose and remediate | | Technical issue | Drop on a specific page type; coincides with deploy or plugin update | Roll back or fix immediately | | Seasonality | Drop matches last year's pattern at the same date | Wait; expected fluctuation | ## 2 Major update types | Update type | What it targets | Recovery | | Core Update | Overall quality, E-E-A-T, helpful content | 3-6 months minimum; usually next core update | | Helpful Content Update | Sites that are mostly AI-generated, thin, or low-effort | 6-12 months; substantial rewriting needed | | Spam Update | Cloaked content, link schemes, doorway pages | Fast if you fix the spam; otherwise won't recover | | Product Reviews Update | Affiliate sites with shallow reviews | Add first-hand evidence, real testing screenshots | | Reviews System Update | All reviews content | First-hand experience signals required | ## 3 How to diagnose 1. 1Plot the drop against the update calendarDid traffic decline start within 72 hours of a confirmed update? If yes, probably algorithm. If no, look elsewhere. 2. 2Check category volatilitySensor tools (Semrush Sensor, MozCast, AccuRanker) show how much movement happened in your category. Volatility > 5 means the update affected your space heavily. 3. 3Identify which page type was hitMost algorithm updates affect specific page types: informational blog posts, comparison pages, affiliate pages. If transactional pages held steady, it's a content-quality update. 4. 4Compare to competitorsDid all competitors drop too, or only you? If only you, look for an on-site cause (E-E-A-T issue, content quality regression, schema problem). If competitors also fell, it's category-wide. ## 4 Realistic recovery options Recovery options ranked by effort and timeline: | Option | Effort | Recovery | | Audit and remove thin content | Medium | 6-9 months | | Add named expert authors with credentials | Medium | 4-8 months | | Rewrite affected pages with first-hand evidence | High | 4-8 months | | Diversify channels (AI engines, email, social) | High | 3-6 months | | Wait for next core update | Low | 3-6 months | Algorithm hits are demoralising, but they're rarely terminal. Most sites that diligently improve content quality recover within 6-9 months — often by the next core update. The sites that don't recover usually have systemic content-quality problems that need a different solution than "more SEO". Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # ASO for Beginners: Optimise Your App Listing Step by Step Learn what ASO (App Store Optimisation) is, which elements of your app listing most affect rankings, and how to improve your ASO score to get more organic downloads. ## What you will learn in this guide - What ASO is and how it differs from SEO - Which app listing elements most affect your store ranking - How to choose keywords for your app title and subtitle - Why screenshots and preview videos affect conversion rate - How to audit your app listing using the free tool ## 1 What is ASO? ASO (App Store Optimisation) is the process of improving your app's visibility in the App Store and Google Play search results. It is to app stores what SEO is to Google — optimising your listing so more people find and download your app organically. ## 2 The most important ASO elements | Element | Ranking impact | Conversion impact | | App title | 🔴 Very high | High | | Subtitle (iOS) | 🟠 High | Medium | | Keywords field (iOS) | 🟠 High | None | | Description | Medium (Google Play) | High | | Screenshots | None | 🔴 Very high | | Preview video | None | 🔴 Very high | | Ratings & reviews | 🟠 High | 🔴 Very high | ## 3 How to audit your app listing 1. 1Run the App Store AuditGo to [app-audit.html](https://aiwebpageseo.com/app-audit.html) and enter your app's App Store or Google Play URL. 2. 2Fix listing quality issues firstMissing subtitle, weak title keywords, no preview video — these are immediate improvements with direct impact on ranking and conversion. 3. 3Review keyword opportunitiesThe audit identifies keywords your competitors rank for that you do not. Add the most relevant ones to your title, subtitle and keywords field. ## 4 Ranking and conversion are two separate problems The table above splits every listing element into ranking impact and conversion impact, and that split is the most useful idea in app store optimisation. Nearly every wasted quarter in ASO comes from confusing the two. Ranking determines how many people *see* your listing. Conversion determines how many of them install. They are driven by almost entirely different elements: the title, subtitle and keyword field decide the first; the screenshots, the preview video and the star rating decide the second. Neither substitutes for the other. So an app ranking tenth and converting at twelve percent will beat an app ranking third and converting at three — and the second team will spend months trying to climb, because rank is the number that looks like the goal. Before you touch a keyword, find out which of the two problems you have. If impressions are healthy and installs are not, no amount of keyword work will help you, and every hour spent on it is an hour not spent on the screenshots. ## 5 The two stores are not one problem Treating iOS and Google Play as the same task with different screenshot dimensions is the most common structural mistake in ASO, and it follows from a genuine difference in how each store indexes a listing. | Field | App Store (iOS) | Google Play | | Title | Indexed, heavily | Indexed, heavily | | Subtitle / short description | Indexed | Indexed | | Keywords field | Indexed — 100 characters, never shown to users | Does not exist | | Long description | **Not indexed** — write it for humans | **Indexed** — write it for both | The consequences are immediate. A team writing a keyword-dense iOS description is writing for an index that does not read it. A team writing a sparse, elegant Play description is leaving indexable surface empty. And the iOS keyword field — a hundred characters no user ever sees — is pure ranking surface with zero conversion cost, which makes it the most under-used asset in most listings. ## 6 The screenshots are the listing Screenshots contribute nothing to ranking and frequently decide the outcome, because they are what people actually look at. Most visitors never read the description; they glance at the first two screenshots, look at the star rating, and decide. So the first two screenshots are doing the work of the entire listing, and the most common failure is that they show the app rather than what the app does for the person. A picture of your settings screen is a picture of a settings screen. A picture of the one thing somebody downloaded your app to accomplish, captioned in five words, is an argument. 1. 1Lead with the outcome, not the interfaceThe first screenshot answers "what will this do for me?" — not "what does the home screen look like?" 2. 2Caption every oneA bare screenshot asks the viewer to work it out; a caption tells them. Set the text large enough to read at thumbnail size, because thumbnail size is where the decision gets made. 3. 3Never oversellA listing promising more than the app delivers produces installs followed by one-star reviews — which lowers the rating, which lowers both ranking and conversion at once. It is the worst outcome available, and it is reached by trying to optimise. ## 7 Ratings: the element that works on both sides at once Ratings and reviews are the only thing on the listing that feeds ranking and conversion simultaneously, and they are the slowest to move. That combination makes them the element most worth a deliberate strategy and the one most often left to chance. The conversion effect is blunt and well understood: a rating visibly below about four stars suppresses installs regardless of how good the screenshots are, because the star count is the one piece of information the visitor believes did not come from you. No amount of listing copy argues with it. The lever is when you ask. An app that prompts for a review on first launch is asking a person who has not yet experienced anything, and the responses reflect that. An app that prompts at a moment of genuine success — the task completed, the thing found, the goal met — is asking somebody who has just been helped, and the difference in both response rate and score is large. The other lever is replying. Public responses to critical reviews are read by the next person deciding whether to install, and a calm, specific reply to a complaint does more for that reader than any positive review does. It also, frequently, gets the original review updated. ## 8 Frequently asked questions The mechanics differ in one respect that changes everything: keyword stuffing is a real and enforced risk in app stores, and it is not on the open web. Apple and Google both operate review guidelines, and a title or description crammed with terms can get a listing rejected or removed — an outcome with no equivalent in organic search, where Google simply ignores what it does not find useful. The second structural difference is that stores separate ranking from conversion far more cleanly than the web does: the keyword field ranks you, the screenshots convert you, and neither does the other's job. Not as a ratio, and this is where habits imported from SEO mislead people. On the web, keyword density is not a ranking factor at all — it is a ratio that rises when you delete text, which is why optimising for it rewards writing less. In an app store there is likewise no magic percentage, but there is a real hazard on the other side: repeating a term to game the index is precisely what the review guidelines prohibit, and enforcement is a human decision rather than an algorithmic shrug. Write the listing for the person deciding whether to install. On iOS: the title, the subtitle and the hundred-character keywords field. The long description contributes nothing to the index, which reliably surprises people arriving from web SEO where body copy is everything. On Google Play the long description does feed the index, which makes the two stores genuinely different optimisation problems rather than one problem with two sets of screenshots. Getting this wrong is the most common structural error in ASO: a keyword-rich iOS description that ranks for nothing, or a sparse Play description that leaves the index half empty. No, and they are frequently the highest-leverage element on the entire listing anyway, because they decide whether the people who already found you install. Hold on to that distinction. Ranking buys impressions; screenshots buy the download. An app ranking tenth and converting at twelve percent beats an app ranking third and converting at three — and the second team will spend a quarter trying to climb, because rank is the number that feels like the goal. Yes, and they are the one element that works on both sides of the funnel simultaneously. They feed store ranking, and they are the strongest single conversion factor on the page: a visible rating below roughly four stars suppresses installs regardless of how good everything else is. They are also the slowest thing to move, which is why asking for a review at a moment of genuine success inside the app — rather than on launch, before the user has experienced anything — is worth more than any amount of listing copy. Change one thing, wait until enough installs have accumulated to say something, then change the next. The temptation is to rewrite the title, subtitle, keywords and screenshots in a single release, at which point you have learned nothing about which change did what — and if installs fall, you cannot tell which one to undo. Both stores offer experiment tooling; use it where you can, and where you cannot, at least leave a gap between changes so the data has a chance to mean something. What is missing, then what is misleading, then what is merely suboptimal. A missing subtitle is unused ranking surface, costing you nothing to fill. Screenshots that do not show the app doing the thing people downloaded it for are a conversion leak that no keyword work will compensate for. And a listing that oversells produces installs followed by one-star reviews, which damages the rating, which damages ranking and conversion at once — the worst available outcome, and one reached by trying to optimise. ASO is one of the most neglected growth channels for app developers. Most apps have obvious listing issues — a missing subtitle, generic screenshots, no preview video — that cost downloads every day. The App Store Audit finds them all in one pass. Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # Backlinks: What They Are and How to Start Building Them Learn what backlinks are, why they are one of the most important ranking factors in Google, and how to start building them for your site. Step by step for complete beginners. ## What you will learn in this guide - What a backlink is and why Google uses them as a ranking signal - The difference between a good backlink and a bad one - What domain authority means and how it is calculated - How to check how many backlinks your site has - The safest and most effective ways to start getting backlinks - What to avoid — link schemes that will get your site penalised ## 1 What is a backlink? A backlink is a link from another website pointing to your website. When a blog post on someone else's site links to one of your pages, that is a backlink. Google treats backlinks as votes of confidence — the more credible sites that link to you, the more Google trusts your site. ## 2 What makes a backlink valuable? Not all backlinks are equal. A link from a well-known, trusted website in your industry is worth far more than a link from a low-quality directory no one reads. | Factor | Why it matters | | Domain authority | Links from high-authority domains pass more ranking power | | Relevance | A link from a site in your industry is more valuable than an unrelated one | | Dofollow vs nofollow | Dofollow links pass authority — nofollow links are noted but pass less | | Anchor text | Descriptive anchor text helps Google understand the context of the link | | Position on page | Links in the main content are worth more than footer or sidebar links | ## 3 How to check your backlinks 1. 1 Open the Backlink Tools Go to [performance-tools.html#backlinks](https://aiwebpageseo.com/performance-tools.html#backlinks) and enter your domain. 2. 2 Review your top backlinks The tool shows your top 100 dofollow backlinks ranked by domain authority. Look at which pages on your site attract the most links — these are your strongest pages. 3. 3 Check for low quality links If you see links from spammy directories or irrelevant sites, make a note. A large number of low-quality links can hurt rather than help your rankings. ## 4 How to start getting backlinks 1. 1 List your business on reputable directories Google Business Profile, Yell, Yelp, Trustpilot, and industry-specific directories are easy first backlinks that also help local SEO. 2. 2 Write genuinely useful content The most reliable way to earn backlinks is to publish content people want to reference — guides, data, tools, or opinions that are genuinely better than what already exists. 3. 3 Guest posting on relevant sites Offer to write an article for another site in your industry in exchange for a link back to your site. Focus on quality sites with real audiences, not link farms. 4. 4 Reclaim unlinked mentions Search for your brand name online. If you find sites that mention your business without linking to you, contact them and ask them to add a link. Backlinks are still one of Google's strongest ranking signals. A site with 10 good quality backlinks will almost always outrank a site with no backlinks and better on-page SEO. This guide explains what makes a backlink valuable and gives beginners a realistic starting point. Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials. # Brand Mention Monitoring: A Beginner's Playbook Learn how to monitor mentions of your brand across the web, classify sentiment, reclaim unlinked mentions for backlinks, and catch crisis-tier negative threads before they go viral. ## What you will learn in this guide - What brand mention monitoring actually tracks - How to classify mentions: positive, neutral, negative - Why unlinked mentions are the easiest backlinks to earn - How to set crisis alerts and respond appropriately - Realistic monthly time commitment ## 1 What brand monitoring tracks Brand mention monitoring finds every public mention of your brand name across: - News sites and trade publications - Social media (Twitter/X, LinkedIn, Reddit, Hacker News) - Blogs and Substacks - YouTube and podcast transcripts - Review sites (G2, Trustpilot, Capterra) - Forums and community boards ## 2 Sentiment classification | Sentiment | Example | Response priority | | Positive | "Just switched to [Brand], much better than [Competitor]" | Thank, reshare, maybe quote in marketing | | Neutral | "[Brand] launched a new feature" | Track for share-of-voice metrics | | Negative | "[Brand] charged me twice for a subscription I cancelled" | Respond within 24 hours with resolution path | | Crisis | "[Brand] just deleted 3 weeks of my work after their v4 update" (412 comments, 180 upvotes) | Respond within 2 hours; escalate to leadership | ## 3 Link reclamation The biggest untapped opportunity in most brand monitoring: mentions of your brand that don't link back to you. These are warm leads for link outreach. 1. 1Filter for unlinked mentionsMentions of "Your Brand" on a third-party site where there is no tag pointing to yoursite.com. 2. 2Prioritise by site authorityHigh-authority unlinked mentions (TechCrunch, Forbes, industry trade pubs) are top priority. Low-authority blog mentions can wait. 3. 3Personalised outreachEmail the author or site editor: "Thanks for mentioning us in [article]. Would you be open to adding a link to our [relevant page]? Happy to share useful data for your readers." Avoid templates. 4. 4Track outreach response ratesExpect 20-40% response rate from real personalised outreach. Below 10% means your outreach is too templated. ## 4 Crisis response 1. 1Set tier-based alertsP0: viral negative thread (>500 comments, trending). P1: trade publication exposé. P2: detailed negative review on G2/Trustpilot. P3: routine complaints. 2. 2P0/P1 SLAAcknowledge publicly within 2 hours. Full response within 24 hours. Don't go silent. 3. 3Don't respond as engineeringCrisis responses are PR, not eng. Even if the issue is technical, the response should be empathetic and human, not defensive. 4. 4Always link to the resolutionWhen you fix the underlying issue, link to a public post-mortem from the original thread. This is the highest-trust gesture you can make. Brand mention monitoring is one of those tools that pays for itself within the first month. The link reclamation alone usually yields 5-20 high-quality backlinks per quarter for an active SaaS or ecommerce brand. The crisis-alerting function is what saves you when something goes wrong. Part of the [aiwebpageseo Suite](/seo-audit-platform.html) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) ### About aiwebpageseo aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical SEO tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials.