Sample report: sag3o.com

Analyzed at Oct 8, 2026, 11:46 AM

This is a real scan of sag3o.com on Oct 8, 2026. Every check and every fix is shown in full.

Pro plan onlyIn your own reports, fixes are part of the Pro plan and up.

Check your site

Overall health

SEO 50% + GEO 25% + AEO 25%

Good

90+ Excellent
75+ Good
60+ Needs work
<60 Critical

SEO

Search Engine Optimization

37/41

Excellent

GEO

Generative Engine Optimization

7/15

Needs work

AEO

Answer Engine Optimization

3/12

Needs work

Dimension radar

Top 5 critical fixes

Brand entity first mention0 Organization schema (GEO)0 Opening paragraph length0 Citation density0 Fact-checkable paragraphs0

Needs fixing (9)

Brand entity first mentionWe check whether your brand name appears near the start of your main content.0 Organization schema (GEO)Whether the page includes machine-readable company details (JSON-LD structured data, invisible to visitors) with your business name, website address, logo, and links to your official profiles elsewhere (sameAs).0 Opening paragraph lengthWe measure the length of the first paragraph of your main content, in characters.0 Citation densityHow many links your page text has to other websites (outside sources), measured per 500 words.0 Fact-checkable paragraphsWhat share of the page's paragraphs include a link to an outside source, so readers can check the claim.0 Updated-at freshnessWhether the page shows a published or updated date (in its structured data or in a date tag on the page), and how long ago the latest one was.0 Last-modified signalWhether the site tells search engines when pages were last updated, either as lastmod entries in the sitemap or a Last-Modified value in the server response.0 Organization schemaWhether the page's structured data (written for machines) describes your business (Organization or LocalBusiness), with at least its name and website URL.0 BreadcrumbList schemaWe look for breadcrumb markup in the page code (BreadcrumbList structured data), which spells out where the page sits, like "Home › Category › This page".50

Could improve (6)

Opening paragraph directnessWe read the first paragraph of your main content (ignoring menus, footer and sidebars) and check whether it gets straight to the page's topic.60 TL;DR / key takeawaysWhether the top of the page has a quick summary: a paragraph starting with “Summary”, “Key takeaways”, “TL;DR” (or the Chinese 摘要／重點), or a bulleted list.60 Concrete data pointsWhether the text contains concrete numbers such as years (2025), percentages (30%), amounts with thousands separators ($1,200) or dates (2025-03).60 Unique-voice markersWhether the text includes first-hand phrases such as “we found”, “we tested”, “in our experience” or “our data shows” (or Chinese equivalents like 我們發現).60 Visible dates on pageWhether the page shows a date, such as when an article was published or last updated.60 Speakable schemaWe look for Speakable markup, a setting that tells voice assistants which parts of the page are good to read aloud.70

Passed (47)

Explicit definition presentWe look for a clear definition sentence on the page: one sentence that says directly what a term is.100 List or table presentWe check whether your main content (ignoring menus, footer and sidebars) has any bulleted or numbered lists, or tables.100 Question-style headingsWe check whether your subheadings (H2, H3) are written as questions, such as "How do I choose coffee beans?" rather than "Choosing coffee beans".100 robots.txt allows GPTBotWhether your robots.txt (the file that tells crawlers which parts of the site they may visit) blocks GPTBot, the crawler OpenAI uses to collect data for training its AI models.100 robots.txt allows ClaudeBotWhether your robots.txt (the file that tells crawlers which parts of the site they may visit) blocks ClaudeBot, the crawler Anthropic uses to collect data for training Claude.100 /llms.txt presentWhether your site has a text file called llms.txt at its root.100 robots.txt allows PerplexityBotWhether your robots.txt (the file that tells crawlers which parts of the site they may visit) blocks PerplexityBot, the crawler the AI search engine Perplexity uses to index pages.100 robots.txt allows Google-ExtendedWhether your robots.txt (the file that tells crawlers which parts of the site they may visit) blocks Google-Extended.100 llms.txt well-structuredWhether llms.txt follows the suggested layout: a first line “# Site name”, a one-line summary starting with “>”, and “## Section” headings that group your important pages.100 Title tag presentWhether the page has a title (the title tag), the text shown on the browser tab and as the blue headline in Google results.100 Title lengthWhether the page title (shown on the browser tab and in Google results) is a sensible length.100 Meta description lengthWhether the page summary (the text under the headline in Google results) is a sensible length.100 No noindex directiveWhether the page is marked "do not index" (noindex), either in the page code or in the server's response.100 Open Graph basicsWhether the page sets its share preview (Open Graph): the title, description, image and URL shown when the link is posted on Facebook or LINE.100 JSON-LD structured data presentWhether the page includes structured data (JSON-LD): a block written for machines that spells out facts like your business name, products or article dates in a fixed format.100 JSON-LD validWhether the structured data on the page (JSON-LD, written for machines) is correctly formatted and readable.100 robots.txt reachableWhether the site has a robots.txt, a small file at the root of the site that tells search engines where they may and may not go.100 HTTP 200 statusWhether the server answers normally when the URL is opened (status code 200, meaning "page OK"), judged on the final page after any redirects.100 Main content word countHow much text the page's main content has, not counting menus, footers and sidebars.100 Broken link ratioWe take the first 20 distinct links in the page's HTML (often the menu; internal and external), check each with a quick request, and count how many are broken and don't open.100 LCP (Largest Contentful Paint)How long it takes for the main image or largest block of text to appear after the page opens (Largest Contentful Paint, LCP), measured in a single simulated mobile test.100 Lighthouse PerformanceThe overall speed score (0–100) from Lighthouse, Google's page testing tool, loading the page as a simulated phone.100 Meta description presentWhether the page has a summary (meta description), the two lines of gray text under the headline in Google results.100 Exactly one H1Whether the page has exactly one main heading (H1, usually the largest text at the top).100 Canonical link presentWhether the page declares its official address (a canonical tag), telling search engines which URL to treat as the real one for this content.100 Canonical self-referencingWhether the official address (canonical) declared on the page points back to this same page.100 robots.txt allows GooglebotWhether the site's robots.txt (the file telling search engines where they may go) blocks Google's crawler from the whole site.100 Viewport meta presentWhether the page sets its mobile display (viewport), so it fits the phone screen without pinching and zooming.100 HTTPS enforcedWhether the site ends up on a secure, encrypted connection (https, the padlock in the address bar).100 INP (Interaction to Next Paint)How quickly the page responds after a visitor taps a button or types (Interaction to Next Paint, INP).100 Lighthouse AccessibilityLighthouse's score (0–100) for how usable the page is for people with disabilities, such as enough text contrast and buttons labeled with their purpose.100 Lighthouse SEOLighthouse's score (0–100) for basic search setup on the page, such as title, description and whether it can be indexed.100 /llms-full.txt with full contentWhether your site offers enough full text for AI tools to read.100 Heading hierarchyWhether the page's headings (H1 to H6, smaller number means higher level) go down in order, for example H2 then H3, without jumping from H2 straight to H4.100 <html lang> attributeWhether the page declares its language (the lang attribute on the html tag, e.g. zh-TW for Traditional Chinese in Taiwan).100 sitemap.xml reachableWhether the site has a sitemap (sitemap.xml), a list of the site's important URLs made for search engines.100 sitemap well-formedWhether the sitemap (the list of URLs for search engines) is correctly formatted.100 Internal link countHow many links on this page point to other pages on your own site (internal links).100 CLS (Cumulative Layout Shift)Whether the layout jumps around while loading, for example an ad suddenly pushing a button down just as you tap it (Cumulative Layout Shift, CLS).100 TTFB (Time to First Byte)How long the server takes to start sending the page after the browser asks for it (Time to First Byte, TTFB).100 Lighthouse Best PracticesLighthouse's score (0–100) for following common web development good practices, such as using a secure connection and not throwing script errors.100 Title differs from H1Whether the page title is word-for-word identical to the main heading on the page (the first H1, the largest heading).100 hreflang values validFor sites with several language versions, whether the tags that link those versions to each other (hreflang) use valid language codes.100 sitemap URL countHow many URLs the sitemap lists (or, for a sitemap index, how many sub-sitemaps).100 Strict-Transport-Security headerWhether the server tells browsers to always use the encrypted connection for this site from now on (HSTS).100 Twitter cardWhether the page sets an X (formerly Twitter) card type (twitter:card), which controls the preview when the link is shared on X.100 Anchor text descriptiveWhether link text says where the link goes, such as "See opening hours", instead of "click here" or "learn more".100

Not applicable (6)