Frequently asked questions

No account is required to start. You get 500 proxy requests per day as a guest — enough to crawl most small to medium sites. Sign in with Google to unlock 2,000 requests per day and persistent scan history that follows you across devices.

Any publicly accessible website. In HTML mode, it fetches the raw server response — ideal for traditional CMS sites (WordPress, Drupal, etc.). In DOM Render mode, it executes JavaScript before extracting content — essential for React, Next.js, Vue, Angular, and other single-page applications where content is injected client-side.

Private pages behind login walls, pages blocked by robots.txt disallow rules, and sites using advanced bot detection may not be fully crawlable.

Yes. After a crawl, click 💾 Save Scan and you'll get a unique URL for that report. Share it with a client, teammate, or bookmark it for later. Anyone with the link can view the report — no login required to view.

If you're signed in, all your scans are stored privately in your account and listed in the History panel. Guest scans are stored anonymously — they remain accessible via their URL but are not listed anywhere.

Yes, completely free to use. There are no paid tiers, no credit card required, and no trial period. Signing in with Google is free and simply increases your daily limit from 500 to 2,000 requests and enables persistent history.

The crawler stops automatically and a modal explains that you've reached your daily limit, when it resets, and how signing in increases it. Any pages already crawled are fully preserved — you can still view and save that partial scan.

In DOM Render mode, fetched HTML is injected into a hidden <iframe> in your browser. The iframe executes all JavaScript on the page, then after 900ms (enough for most frameworks to render), sends the final rendered DOM back to the crawler via postMessage. Extraction then runs on the rendered output rather than the raw server HTML.

This is slower (roughly 1-2 seconds per page versus 200-400ms in HTML mode) but accurately reflects what search engines see when they render your JavaScript.

Yes. The project is a standard PHP + vanilla JavaScript stack. You need PHP 7.4+ with the pdo, pdo_sqlite, and curl extensions. Upload the files to any web host, configure your Google OAuth credentials in api/auth.php, make api/scans/ and api/data/ writable, and it's ready. See the README for full deployment instructions.

All scan data is stored on the server as JSON files — in scans/public/ for anonymous saves and scans/users/{id}/ for signed-in users. Only you can see your scans when signed in. Anonymous scans are accessible via their unique URL but are not listed anywhere publicly. User accounts and sessions are stored in a SQLite database.

We do not share, sell, or analyse your scan data. On a self-hosted install, all data stays entirely on your own server.

The title tag is the clickable blue link in search results. Google uses it as a primary signal for what a page is about. It should be 50–60 characters, unique to each page, and contain the target keyword near the front.

The meta description is the grey snippet below the title. It doesn't directly affect rankings but strongly influences click-through rate — a compelling description brings more visitors. Keep it 140–160 characters. Google sometimes rewrites it, but a well-written one is used more often.

A canonical tag (<link rel="canonical" href="...">) tells search engines which version of a page is the "official" one when the same content is accessible at multiple URLs — for example, with and without a trailing slash, or with and without query parameters. Without canonicals, search engines may split ranking signals across duplicate URLs, weakening all versions.

Every page should have a self-referencing canonical tag pointing to its own preferred URL.

An orphan page is one with no internal links pointing to it from the rest of your site. Search engine crawlers discover pages by following links — if no link points to a page, crawlers may never find it, and it will never rank. Fix orphan pages by adding at least one contextually relevant internal link from another page on your site.

The Schema section in the Report tab shows every JSON-LD schema type found across your site — Article, Product, FAQPage, BreadcrumbList, etc. — along with how many pages use each type. It also flags pages with no schema at all.

You can assign a page type (Homepage, Article, Product, FAQ, etc.) to any page and the tool will show you the recommended schema markup and a ready-to-copy JSON-LD template for that type.

Select any page in the sidebar and click the Content tab to see: total word count, sentence count, average words per sentence, Flesch reading ease score (0 = very difficult, 100 = very easy), reading level label, internal link count, external link count, content length rating, the introduction paragraph, and the top 10 key phrases ranked by frequency with their density percentage.

Go to the Action Report tab (last tab). It lists every issue across SEO, AEO, and GEO, sorted by severity. Fix errors first (red — each one costs 20 points), then warnings. The report groups issues by page so you can work through one URL at a time without jumping around.

SEO optimises for ranking — getting your page into the top results list. AEO optimises for being quoted — getting your page selected as the direct answer. The two overlap but require different execution:

• SEO cares about keyword density and backlinks. AEO cares about question-framed headings and direct answer paragraphs.
• SEO uses broad, informational meta descriptions. AEO needs concise 40–60 word paragraphs that could stand alone as answers.
• SEO benefits from long-form content. AEO requires scannable, structured content with clear Q&A patterns.

Both matter — a page needs to rank before it can be chosen as an answer.

Yes. Google's AI Overviews (formerly Search Generative Experience) appear in regular text search results on desktop and mobile — not just voice. When Google shows an AI-generated answer at the top of results and cites a source, the cited page can receive a significant traffic spike. AEO-optimised pages are more likely to be cited as that source.

Google's featured snippet box holds roughly 45–50 words comfortably. Paragraphs in this range are short enough to reproduce in full (which is what Google does for "paragraph snippets") but long enough to actually answer a question. Paragraphs under 40 words are often incomplete. Paragraphs over 60 words get truncated — the trailing "..." reduces click appeal and often signals to Google that the answer isn't crisp enough.

Place these concise paragraphs immediately after a question-framed heading for maximum snippet eligibility.

Yes. Product pages should answer the questions buyers ask: "What does this product do?", "Who is it for?", "How much does it cost?", "What are the system requirements?". Framing your product page sections as questions and adding concise answer paragraphs — along with FAQPage or Product schema — can significantly improve AEO on commercial pages, not just informational ones.

AEO is about getting your content quoted in a specific answer to a specific question — one page, one answer, one moment. It's reactive (triggered by a query) and structural (depends on content format).

GEO is about becoming the type of source that AI systems treat as credible and citable across many queries — even ones not directly about your topic. It's about building the signals that LLMs use to assess whether a source is worth referencing: attribution, dates, facts, authority, and originality.

A page can score well on AEO with good structure but poorly on GEO if it lacks an author, has no dates, and contains no original data.

If your potential customers or audience use AI tools to research — yes, regardless of industry. Research from BrightEdge and others shows that AI-influenced search now affects significant percentages of discovery journeys in B2B, healthcare, finance, legal, education, and consumer markets. If a buyer asks ChatGPT "what's the best accounting software for small businesses" and your product isn't in the answer, you've missed a lead that never saw your site.

LLMs are trained on data up to a cutoff date, but retrieval-augmented systems (like Perplexity and Bing Copilot) fetch live content. These systems heavily filter for recency because outdated information can cause them to produce incorrect answers — something they are specifically designed to avoid.

A page with no datePublished in its schema is treated as potentially stale regardless of when it was actually written. A page with a recent dateModified signals that it's been reviewed and updated, which is a strong positive signal.

Ask directly. Open ChatGPT, Perplexity, or Claude and ask a question that your content directly addresses. If your site appears in the cited sources, you're already being picked up. If not, note what sources are being cited and study their content structure — they're doing something your pages aren't yet.

Perplexity is particularly useful for this research because it shows explicit inline citations, making it easy to see exactly which pages it favours for which types of queries.

No — the two are almost entirely complementary. Author attribution, clear dates, factual density, authoritative outlinks, and Organisation schema are all positive SEO signals too. GEO improvements are an extension of E-E-A-T (Experience, Expertise, Authoritativeness, Trust) — Google's framework for assessing content quality, which is already central to modern SEO.