' tag, the main heading ('<h1>'), or the first paragraph. This weakens the signal about which entity the page is primarily about and makes it harder for LLMs to connect the page to your brand or product.","context":"This task is triggered when the configured brand or product name does not appear in the '<title>', '<h1>', or the first text block of the page, especially on critical templates such as homepage, product, about, contact, or careers pages. For LLMs, this reduces entity clarity and brand presence in answers.","recs":{"titleMention":"Include your brand and/or product explicitly in the '<title>' tag (e.g. \"{brand} – {product} for {useCase}\"). This gives crawlers and LLMs a clear entity signal.","firstParagraphMention":"Mention the brand/product in the first paragraph in natural language (e.g. \"{brand} is…\") so LLMs interpret it as a stable entity reference."}},"keyphrases":{"title":"Insufficient topical depth and semantic coverage","description":"Key target phrases {phrases} are underused or missing. LLMs rely on semantic density (topic clusters, synonyms, variations) to understand relevance and authority. Without these signals, your page is less likely to be treated as an authoritative source for this topic.","context":"This task is triggered when the target keyphrases derived from project context and page type are not found or only minimally present in '<title>', '<h1>', the first paragraph, and the early body text. The check is tolerant to light variations (plural/singular, hyphen vs. space).","recs":{"includePhrases":"Integrate the target terms {phrases} naturally into headings ('<h2>', '<h3>') and body copy. Build meaningful topic clusters instead of mentioning each phrase only once.","matchIntent":"Extend your content to cover typical user intents (e.g. \"What is…?\", \"How does… work?\", \"Pros/cons\") using synonyms and long-tail variations. This helps LLMs classify the page as a comprehensive resource."}},"tableOfContents":{"title":"Missing Table of Contents","description":"This long-form content (>1500 words) lacks a Table of Contents with anchor links, which makes it harder for users and AI systems to understand the structure and jump to specific sections.","context":"This task is triggered when the estimated word count exceeds ~1500 words, multiple subheadings ('<h2>'/'<h3>') are present, but no ToC pattern is detected near the top of the page (e.g. a \"Contents\" / \"Table of Contents\" block with internal #anchor links). For LLMs, a clear ToC improves section detection and deep-linking to specific subtopics inside a long article.","recs":{"addTableOfContents":"Add a prominent Table of Contents near the beginning of the article (typically right after the '<h1>') that lists the main '<h2>'/'<h3>' sections.","useAnchorLinks":"Use in-page jump links (e.g. '<a href=\"#section-intro\">Introduction</a>') and matching IDs on headings (e.g. '<h2 id=\"section-intro\">…</h2>') so users and AI systems can jump directly to specific sections.","keepToCInHtml":"Implement the ToC as real HTML (e.g. '<nav aria-label=\"Table of contents\"><ul>…</ul></nav>') rather than only visually in the template, so crawlers and LLMs can reliably detect the structure."}},"definitiveAnswer":{"title":"Missing definitive answer after question headings","description":"Headings formulated as questions are not directly followed by a concise answer paragraph. This lowers the chance of being used as a direct answer (e.g. Featured Snippet or LLM short answer).","context":"This task is triggered when headings ending with a question mark or containing typical question patterns (e.g. \"How…?\", \"What is…?\") are detected, but the immediately following paragraph is either missing or too long/indirect. LLMs prefer short, precise answer snippets immediately after the question and use the following text for deeper explanation.","recs":{"addAnswerAfterQuestion":"Place a clear, standalone answer paragraph (roughly 20–80 words) immediately after each question heading before going into more detail.","keepAnswersConcise":"Avoid fluff, disclaimers, or long introductions in the first 1–2 sentences after a question. Start with the actual answer; examples, background and nuance can follow afterwards.","reuseForFAQ":"Apply this pattern (question heading + short direct answer paragraph) to FAQ-style sections as well to increase your chances of being surfaced as a direct answer in AI systems."}},"urlStructure":{"title":"Non-semantic URL structure","description":"The URL contains underscores, uppercase letters, excessive depth, or mostly technical fragments (IDs, parameters). Such URLs are harder to read for users and provide weaker topical signals to LLMs.","context":"This task is triggered when the path includes underscores (\"_\"), uppercase letters, more than about three directory levels, or primarily technical patterns (e.g. /post?id=1234 or /category/1234-abc/). Clean, semantic slugs help LLMs infer the main topic and entities of a page directly from the URL.","recs":{"useHyphens":"Use lowercase letters and hyphens instead of underscores (e.g. /ai-seo-check/ instead of /AI_SEO_Check/). This improves readability and consistency.","keepFlat":"Keep the URL depth as flat as reasonably possible (ideally no more than 3 levels deep, e.g. /blog/ai-seo-basics/) instead of deeply nested paths.","useSemanticSlugs":"Use human-readable, topic-focused slugs that include key terms and entities (e.g. /products/ai-seo-plugin/ instead of /products/item-123/). Avoid unnecessary parameters and opaque IDs wherever possible."}}},"eta":{"authorityLinks":{"title":"Missing trust-by-association signals","description":"No external links to trusted domains (e.g. .gov, .edu, official organizations) were found. Such references signal to LLMs that your content is well-researched and embedded in a reliable information network.","context":"This task is primarily triggered on knowledge-type pages (e.g. blog, case studies) when no outbound links to authoritative domains are present. For LLMs, this weakens the impression that your content is well-supported and citable.","recs":{"includeTrustedSources":"When you cite facts, statistics, or studies, link to original, reputable sources using standard '<a href=\"…\">' links in the body content.","useAuthoritativeDomains":"Prefer links to highly trusted domains (e.g. .gov, .edu, reputable industry bodies), as these create strong trust-by-association signals for LLMs."}},"authorBio":{"title":"Missing author bylines or bios","description":"No clear author attribution (byline) or structured author information (meta tag, schema, author block) was found. LLMs score content with identifiable experts higher, especially for advisory or explanatory topics.","context":"This task is triggered when article-like pages (e.g. blog, case study) lack any author signals – no '<meta name=\"author\">', no schema.org author property, and no visible byline near the article.","recs":{"addAuthorNearContent":"Add a visible byline close to the title or introduction (e.g. '<p class=\"author\">By {name}</p>') using clear patterns like \"By\" or \"Von\".","includeBioWithCreds":"Add a short author bio with role, expertise, and optionally a link to a profile page (e.g. /team/{author}) and mirror it in Article schema (\"author\": { \"@type\": \"Person\", \"name\": \"…\" })."}},"trustSignals":{"title":"Missing experience or trust signals","description":"No clear trust signals such as client logos, testimonials, reviews, certifications, or case studies were detected. LLMs factor these into decisions about which providers or solutions to recommend.","context":"This task is triggered mainly on product, service, and about pages when no visual or textual evidence of real clients, projects, or awards is present and no review/rating schema can be found.","recs":{"includeSocialProof":"Add client logos, testimonials, review snippets, or award badges to your HTML and describe them in text (e.g. \"Awarded by…\").","linkToCaseStudies":"Link to dedicated case study or reference pages using descriptive anchors such as \"Case Study: {client}\" so LLMs can follow those relationships."}},"footerLinks":{"title":"Missing About or Contact pages","description":"The page is missing visible or linked \"About\" or \"Contact\" pages via typical footer or header links. This weakens transparency and trust signals for both LLMs and users.","context":"This task is triggered when no internal links whose URL or anchor pattern suggests About/Contact/Imprint/Legal pages can be found in the footer or header. LLMs then have less evidence about who operates the website.","recs":{"addAboutAndContactLinks":"Add internal links in footer (and optionally header) to /about, /contact, /imprint, /privacy, /terms, etc., using clear link labels such as \"About\" or \"Contact\".","includeCompanyDetails":"Ensure these pages contain address, contact options (email, phone), and legal details, ideally supported by Organization schema."}},"schemaEnrichment":{"title":"Missing E-E-A-T Schema Properties","description":"Your Person or Organization schema is missing key properties that communicate experience, expertise, authority, and transparency to AI systems. Without fields like alumniOf, knowsAbout, hasCredential, or award, LLMs have fewer structured signals to understand why you should be treated as a trustworthy, expert source.","context":"This task is triggered when a Person or Organization JSON-LD block is present, but important E-E-A-T-related properties are missing. The checker looks for @type \"Person\" or \"Organization\" and then inspects fields like alumniOf, hasCredential, knowsAbout, award, sameAs, publishingPrinciples, and ownershipFundingInfo. For LLMs, these properties act as explicit, machine-readable proof of qualifications, specializations, and editorial standards – not just marketing claims in plain text.","recs":{"addAlumniOf":"Add an \"alumniOf\" property for Person entities to reflect educational background (e.g. university, business school). Use either a plain text string or a nested Organization object.","addHasCredential":"Use \"hasCredential\" to model degrees, certifications, or professional licenses (e.g. ISO auditor certification, medical license) as structured data instead of just mentioning them in prose.","addKnowsAbout":"Populate \"knowsAbout\" with specific topics and domains (e.g. \"AI-SEO\", \"pharmaceutical supply chain\"). Where possible, point to canonical identifiers such as Wikidata URLs to strengthen entity linking.","addAward":"Add an \"award\" property listing notable awards, rankings, or recognitions your brand or experts have received (e.g. industry prizes, \"Top 100\" listings).","addPublishingPrinciples":"Expose your editorial standards via the \"publishingPrinciples\" property, linking to a public page that describes your review, fact-checking, conflict-of-interest, and update policies.","addOwnershipFundingInfo":"Use \"ownershipFundingInfo\" to disclose ownership structure, investors, or funding sources. This helps AI systems evaluate potential biases and improves perceived transparency.","addSameAs":"Use \"sameAs\" to link to verified external profiles (e.g. LinkedIn, official social accounts, Crunchbase, Wikipedia). This strengthens entity resolution and cross-checking in LLM training data.","keepConsistent":"Ensure that the names, roles, and organizations in your schema match the names and roles used on the page and across your site (no conflicting job titles or brand names)."}},"firstPersonDensity":{"title":"Low Experience Signals (First-Person)","description":"This content type (e.g., blog post, review, case study) uses very little first-person language (\"I\", \"we\", \"our\"), even though the topic suggests real-world experience. LLMs increasingly look for explicit experience cues to distinguish hands-on expertise from pure summary or affiliate-style content.","context":"This task is triggered when the page is classified as experience-heavy content (blog/review/guide) but the ratio of first-person pronouns in the main body text stays below a defined threshold. The checker scans for patterns like \"I\", \"we\", \"our\", \"my\" (and equivalents in the page language). For LLMs and modern search systems, clear first-person signals combined with concrete details are an important part of the \"Experience\" in E-E-A-T.","recs":{"usePersonalLanguage":"Where appropriate, switch from purely generic phrasing to more personal language that shows a real human is speaking (e.g. \"In our tests…\", \"In my experience…\").","useFirstPersonLanguage":"Add first-person pronouns (I, we, my, our) in sections that describe tests, projects, or client work – but only where this reflects actual experience, not fabricated claims.","sharePersonalExperience":"Explicitly describe what you or your team did, saw, or measured (e.g. \"We implemented this on 12 client sites\" or \"I ran this setup for 3 months before…\") instead of just summarizing general advice.","addConcreteDetails":"Strengthen experience signals by adding concrete details such as time frames, tools, metrics, and context (e.g. \"using GA4\", \"in a clinical setting\", \"with Shopify stores\"). This helps LLMs differentiate lived experience from generic content.","stayAuthentic":"Avoid artificially stuffing first-person phrases. Focus on authentic, verifiable experience and keep tone consistent with your brand and legal/compliance requirements."}}},"faq":{"schemaMissing":{"title":"Missing programmatic FAQ understanding","description":"FAQ-like content was detected (questions & answers), but no schema.org/FAQPage markup is present. LLMs can only see these as plain text, not as structured Q&A units.","context":"This task is triggered when headings or patterns such as \"FAQ\" / \"Frequently asked questions\" are detected, but there is no @type \"FAQPage\" in any JSON-LD block.","recs":{"implementJsonLD":"Implement a FAQPage schema in JSON-LD format in the '<head>' or near the end of the '<body>', using \"@type\": \"FAQPage\" and a mainEntity array of Question/Answer objects.","ensureSyntax":"Use the correct structure: each question as { \"@type\": \"Question\", \"name\": \"…\", \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"…\" } }. Validate using Google's Rich Results Test."}},"schemaInvalid":{"title":"Invalid or Incomplete FAQPage Schema","description":"An FAQPage schema was detected, but it contains structural errors or is missing required properties. Broken JSON-LD is ignored by search engines and AI systems, so you lose all potential FAQ rich result and AI visibility benefits.","context":"This task is triggered when a JSON-LD block declares @type \"FAQPage\" but fails basic validation: for example, mainEntity is missing or not an array, Question/Answer objects are incomplete, required fields like \"name\" or \"acceptedAnswer\" are missing, or the JSON itself is syntactically invalid. LLMs and search engines will typically ignore such schemas completely rather than partially interpreting them.","recs":{"validateStructure":"Check that your FAQPage JSON-LD follows the structure faq: { \"@type\": \"FAQPage\", \"mainEntity\": [ { \"@type\": \"Question\", \"name\": \"…\", \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"…\" } } ] }. Ensure mainEntity is an array of Question objects with acceptedAnswer.","useValidator":"Always validate your final schema in tools like Schema Markup Validator, Rich Results Test, or Search Console before deploying. Fix all reported errors and critical warnings.","fixRequiredFields":"Ensure every Question has a \"name\" and every Answer has a \"text\" field. Avoid leaving placeholders like \"Lorem ipsum\" or \"TODO\" in production data.","avoidMixedTypes":"Do not mix multiple unrelated @type values inside the same JSON-LD block (e.g. FAQPage + Product). Use separate JSON-LD blocks per logical entity to avoid parsing issues.","keepJsonValid":"Make sure the JSON is syntactically valid: no trailing commas, correct quotes around keys and values, and properly escaped special characters (e.g. quotes in question text)."}},"missingTags":{"title":"Missing FAQ expand/collapse tags","description":"FAQ content was found, but it is not wrapped in semantic '<details>'/'<summary>' tags. This makes it harder for LLMs and assistive tech to identify question-answer blocks.","context":"This task is triggered when FAQ-style headings or Q&A structures are present, but there are no '<details>' elements in the HTML even though a collapsible FAQ UI is expected.","recs":{"wrapInDetails":"Wrap each question/answer pair in a '<details>' element with a '<summary>' for the question and a block element (e.g. '<p>') for the answer.","correctStructure":"Use a clean pattern such as '<details><summary>Question…</summary><div>Answer…</div></details>' to improve both UX and machine understanding."}},"unstructured":{"title":"Unstructured FAQ detected","description":"FAQ-like content was identified via pattern matching (e.g. question-form headings) but without semantic markup or FAQPage schema. LLMs can reuse this content less reliably as standalone Q&A snippets.","context":"This task is triggered when multiple question-like headings or Q&A patterns exist, but no '<details>'/'<summary>' and no schema.org/FAQPage markup are present in the DOM.","recs":{"useDetails":"Format question/answer pairs using '<details>'/'<summary>' or a consistent Q&A HTML pattern (e.g. '<h3>Question</h3><p>Answer</p>').","addFAQSchema":"Add a FAQPage JSON-LD schema that covers the most important visible Q&A pairs and validate it with Google's Rich Results Test."}}},"freshness":{"visibleDate":{"title":"Missing visible freshness signals","description":"No visible \"Published on\" or \"Last updated\" date was found. Without dates, LLMs and search engines cannot distinguish whether content is current or outdated.","context":"This task is triggered when no date pattern can be detected in the visible content near the article title, header, or meta area. It is especially relevant for news, blogs, and knowledge articles.","recs":{"displayDate":"Place a clearly visible \"Published on\" or \"Last updated\" date near the title or introduction, e.g. in a '<time>' element or a '<span class=\"post-date\">'…'</span>'.","placeNearTop":"Ensure the date is shown in the upper part of the page so LLMs and users can quickly assess content recency."}},"timeTag":{"title":"Missing machine-readable '<time>' tag with datetime","description":"A visible date was detected but is not marked up with a '<time>' element including a datetime attribute. LLMs and search engines cannot reliably parse date information without machine-readable markup.","context":"This task is triggered when a date format is detected in text but no matching '<time datetime=\"…\">' element is present in the HTML.","recs":{"wrapInTime":"Wrap all important dates in '<time>' tags, e.g. '<time datetime=\"2024-05-21\">May 21, 2024</time>'.","addDatetime":"Use the datetime attribute in ISO 8601 format (YYYY-MM-DD or with time) so machines can parse and compare dates robustly."}},"metaTag":{"title":"Missing last-modified meta tags","description":"No '<meta name=\"last-modified\">' or '<meta property=\"article:modified_time\">' tag was found. These tags give crawlers a direct hint about when a page was changed.","context":"This task is triggered when visible dates exist but there are no corresponding meta tags in the '<head>' that indicate modification timestamps.","recs":{"addMetaTag":"Add '<meta name=\"last-modified\" content=\"2024-05-21\" />' or '<meta property=\"article:modified_time\" content=\"2024-05-21T10:30:00+02:00\" />' to the '<head>'.","keepUpdated":"Update these meta values automatically whenever content changes, so LLMs always see accurate freshness information."}},"sitemapLastmod":{"title":"Missing '<lastmod>' in sitemap","description":"Your sitemap.xml is missing '<lastmod>' tags for URL entries. Without this, crawlers and LLMs cannot easily prioritize which pages are fresh and important.","context":"This task is triggered when a sitemap is present but '<url>' blocks do not contain '<lastmod>' tags or use implausible dates.","recs":{"addLastmodTags":"Add a '<lastmod>' tag to each '<url>' entry in sitemap.xml (e.g. '<lastmod>'2024-08-25'</lastmod>').","useISODate":"Use ISO 8601 dates and keep them in sync with actual content changes.","checkCMSSettings":"Configure your CMS or sitemap plugin to maintain '<lastmod>' values automatically instead of hard-coding them."}},"sitemapUrlLastmod":{"title":"Missing '<lastmod>' in Sitemap Entry","description":"This URL is listed in your sitemap.xml but its '<url>' entry does not contain a '<lastmod>' tag. Without this timestamp, search engines and AI crawlers have weaker signals about when this specific page was last updated and how fresh its content is compared to other URLs.","context":"This task is triggered when a matching '<loc>' entry for this URL is found in sitemap.xml but the corresponding '<lastmod>' tag is missing, empty, or not in a valid date format. For LLMs and modern search systems, per-URL '<lastmod>' timestamps help prioritise crawling, recency-sensitive answers, and AI search features that highlight up-to-date sources.","recs":{"addLastmodToEntry":"Add a '<lastmod>' tag inside the '<url>' block for this page in your sitemap.xml, for example: '<lastmod>'2025-01-15'</lastmod>'.","useISODateFormat":"Use a valid ISO 8601 date format (e.g. 2025-01-15 or 2025-01-15T10:30:00+00:00) to ensure all crawlers can parse the value correctly.","updateOnContentChange":"Update the '<lastmod>' value whenever you significantly modify the page content, not just on minor layout tweaks, so AI systems understand when substantive information changed.","alignWithPageSignals":"Keep the '<lastmod>' date consistent with other freshness signals (e.g. visible \"Last updated\" text, modified_time meta tags) to avoid conflicting signals about recency.","automateSitemapGeneration":"If possible, configure your CMS or sitemap generator plugin to automatically maintain '<lastmod>' values based on real content changes, reducing manual work and errors."}},"lastModifiedMeta":{"title":"Missing Last Modified Meta Tag","description":"No '<meta name=\"last-modified\">' or '<meta property=\"article:modified_time\">' tag was found in the '<head>' of this page. These meta tags provide machine-readable freshness signals that help search engines and AI systems understand when the content was last updated.","context":"This task is triggered when the page has indexable content but no last-modified style meta tags in the '<head>'. While server headers and sitemaps can also carry freshness information, explicit meta tags like name=\"last-modified\" or property=\"article:modified_time\" give LLMs and search engines a clear, per-page timestamp directly tied to the HTML document.","recs":{"addMetaTag":"Add either '<meta name=\"last-modified\" content=\"2025-01-15T10:30:00+00:00\">' or '<meta property=\"article:modified_time\" content=\"2025-01-15T10:30:00+00:00\">' to the '<head>' section of the page.","keepUpdated":"Ensure the meta value is updated whenever the main content changes (e.g. via your CMS or build pipeline) so AI systems don't treat outdated content as fresh.","useISODateTime":"Provide the timestamp in ISO 8601 format including time and timezone where possible (e.g. 2025-01-15T10:30:00+01:00) to avoid ambiguity.","syncWithSitemap":"Keep the meta modified time in sync with the '<lastmod>' value in sitemap.xml for this URL to avoid conflicting freshness signals.","avoidFakeFreshness":"Do not update these timestamps artificially without real content changes. AI systems and search engines may downgrade sites that appear to manipulate freshness signals."}}},"headerFooter":{"tags":{"title":"Missing semantic header/footer structure","description":"The page is missing semantic '<header>' and/or '<footer>' elements. Without them, crawlers and LLMs cannot clearly separate global navigation, branding, and footer from main content.","context":"This task is triggered when typical header and footer patterns (logo, navigation, legal links, copyright) are detected but not wrapped in '<header>' or '<footer>' elements.","recs":{"wrapHeader":"Wrap the global top section (logo, main navigation, main CTA) in a '<header>' element, e.g. '<header>'…'</header>'.","wrapFooter":"Use a '<footer>' element for legal links, contact info, and copyright, so LLMs can treat this as a trust and context block."}},"headerEntity":{"title":"Missing Header Branding","description":"The '<header>' tag exists, but it does not clearly expose your brand as a recognizable entity (no site name in a heading and no logo image with meaningful alt text). This weakens the primary branding signal that AI systems use to understand which organization is behind the content.","context":"This task is triggered when a '<header>' element is present but no strong branding elements can be detected: no '<h1>'/'<h2>' with a site or brand name, and no '<img>' logo in the header with alt text that matches the brand. For LLMs and search engines, a clearly branded header is a key cue to map the page to a specific Organization or WebSite entity, align it with your Organization schema, and distinguish your brand from other domains or resellers.","recs":{"addH1":"Add a heading element in the header (ideally '<h1>' on the homepage, '<h2>' or '<div>' with role=\"heading\" on subpages) that contains your brand or site name in a clean text form (e.g. \"GAISEO – AI-SEO Platform\").","addLogo":"Include a logo image inside the '<header>' wrapped in a link to the homepage (e.g. '<a href=\"/\">' '<img src=\"/logo.svg\" alt=\"Your Brand Name\">' '</a>'). Make sure the alt text clearly states the brand name, not just \"logo\".","matchBrandName":"Ensure that the brand name in the header text and logo alt attribute matches the name used in your Organization schema (JSON-LD) and across other pages. Consistent naming makes entity resolution easier for AI systems.","useSemanticContainer":"Keep your primary branding elements inside the '<header>' element (logo, brand name, main navigation). Avoid scattering branding across multiple unrelated containers, which makes structural parsing harder.","supportAccessibility":"Use aria-label or aria-labelledby on the '<header>' if needed (e.g. '<header aria-label=\"Main site header\">') and ensure that the logo link has a descriptive alt or aria-label, improving both accessibility and machine understanding.","avoidTextInImagesOnly":"Do not rely solely on text embedded in images for your brand name. Always provide a text node (heading or span) with the brand name so AI and screen readers can read it reliably."}},"schema":{"title":"Missing organization identity for AI systems","description":"No Organization schema was found in the JSON-LD blocks. Without @type \"Organization\", LLMs lack a strong signal about who stands behind the website.","context":"This task is triggered when there is no Organization schema on domain-level or key pages (e.g. homepage, about), or when the schema is present but missing core properties such as name/url/logo.","recs":{"addBlock":"Add a JSON-LD block with \"@type\": \"Organization\" to your homepage (usually in the '<head>') using \"@context\": \"https://schema.org\".","includeFields":"Fill important properties like name, url, logo, address, contactPoint, and sameAs (links to social profiles) so LLMs can anchor your brand as a stable entity."}},"transparency":{"title":"Incomplete footer transparency signals","description":"The footer is missing key transparency signals such as links to Contact, About, Imprint/Legal, Privacy, or an address and copyright. This makes risk assessment harder for LLMs.","context":"This task is triggered when the footer contains few or no legal/trust-related elements and no recognizable link texts or patterns that indicate such pages.","recs":{"addLegalLinks":"Include links like \"About\", \"Contact\", \"Imprint\", \"Privacy\", and \"Terms\" in the footer with clear labels.","showAddress":"Display a full company address and at least one working contact channel (email or phone).","showCopyright":"Add a visible copyright notice such as \"© {year} {brand}. All rights reserved.\" and keep the year up to date."}}},"technicalAiSeo":{"fetchpriority":{"title":"Missing LCP Prioritization","description":"No image on the page uses fetchpriority=\"high\". Without explicitly prioritising the Largest Contentful Paint (LCP) image, the browser may load it later than needed, slowing perceived performance for both users and AI-driven performance audits.","context":"This task is triggered when no '<img>' or '<link rel=\"preload\" as=\"image\">' element for the main hero/LCP image is using fetchpriority=\"high\". Modern browsers use this hint to load the most important above-the-fold image earlier in the critical path. Since Core Web Vitals (especially LCP) are a strong quality signal that AI systems factor into ranking and evaluation, missing fetchpriority on the hero image can lead to slower LCP and weaker performance scores.","recs":{"addToHero":"Identify the main above-the-fold hero image (the likely LCP element) and add fetchpriority=\"high\" to its '<img>' tag, e.g. '<img src=\"hero.jpg\" fetchpriority=\"high\" ...>'.","combineWithPreload":"For critical hero images, consider combining fetchpriority=\"high\" with '<link rel=\"preload\" as=\"image\" href=\"/path/hero.jpg\">' in the '<head>' to further tighten the loading sequence.","useSelectively":"Apply fetchpriority=\"high\" only to a single, truly critical image above the fold. Using it on multiple images reduces its effect and may compete with other important resources.","monitorLcp":"After implementation, measure LCP using tools like Lighthouse, PageSpeed Insights or Web Vitals in the browser to confirm that the change improved your LCP timing on real devices.","avoidNonCriticalUse":"Do not use fetchpriority=\"high\" on images that are lazy-loaded, below the fold, or not visually central to the first viewport – this can waste bandwidth and harm overall performance."}},"fontPreload":{"title":"Missing Font Preloading","description":"Critical web fonts used in above-the-fold text are not preloaded. This can cause layout shifts, flash of invisible text (FOIT/FOUT) and slower First Contentful Paint (FCP), all of which negatively affect perceived quality for users and AI performance evaluators.","context":"This task is triggered when fonts used for main UI text or headings (e.g. '<h1>', navigation) are loaded only via @font-face or CSS, but there is no corresponding '<link rel=\"preload\" as=\"font\">' entry in the '<head>'. Without explicit preloading, the browser may delay fetching fonts until later in the render pipeline, causing late text rendering and cumulative layout shift.","recs":{"preloadCriticalFonts":"Add '<link rel=\"preload\" as=\"font\" type=\"font/woff2\" href=\"/path/font.woff2\" crossorigin>' for your primary text and heading fonts that appear above the fold.","includeCrossorigin":"Always include crossorigin=\"anonymous\" (or the appropriate value) on preloaded fonts so the preload can be reused by the @font-face request and not double-download.","limitToKeyFonts":"Preload only the most important fonts (primary regular and bold weights) that are visible on initial view. Avoid preloading every variant to prevent blocking other critical resources.","matchCss":"Ensure that the href in the preload link exactly matches the src URL used in your @font-face declaration (same path, protocol, and query parameters).","testLayoutShift":"After adding preloads, check CLS (Cumulative Layout Shift) and FCP metrics and visually verify that text appears quickly without flicker or late reflows."}},"codeRatio":{"title":"Low Text-to-Code Ratio","description":"Only {ratio}% of your page is actual text content. A very low text-to-code ratio makes it harder for AI crawlers to extract meaningful signals from your HTML, because the relevant content is buried under markup, inline scripts, and styling.","context":"This task is triggered when the ratio of visible text content to total HTML document size drops below a defined threshold. Pages with excessive inline CSS/JS, nested wrappers, or large script blocks but little semantic text provide weak training material for LLMs. AI systems looking for high-quality, information-dense sources may downgrade or ignore pages where content is sparse compared to boilerplate code.","recs":{"reduceInline":"Move large inline '<style>' and '<script>' blocks into external .css and .js files where possible, and minify them. Keep the HTML document focused on semantic structure and content.","removeDeadCode":"Audit your templates for unused components, commented-out HTML, and legacy scripts that can be safely removed to reduce noise.","writeMoreContent":"Increase the amount of high-quality, human-readable text (headings, paragraphs, lists) that explains your topic in depth. Aim for a meaningful body of content, not just a thin landing page.","useSemanticTags":"Wrap content in semantic tags ('<article>', '<section>', '<p>', '<ul>', '<ol>', '<figure>') so AI crawlers can easily separate real content from layout boilerplate.","avoidOverNestedMarkup":"Simplify overly nested '<div>' structures and utility wrappers where possible. Cleaner DOM hierarchies make it easier for both traditional crawlers and LLM-based parsers to understand your page.","monitorTemplateBloat":"If many pages show a low text-to-code ratio, review your CMS or frontend framework patterns (e.g. excessive components, duplicated markup) and refactor to reduce template bloat."}}},"headings":{"h1":{"title":"Incorrect '<h1>' usage","description":"Your page should contain exactly one H1 element that represents the primary topic. Currently found: {count}. Multiple or missing '<h1>' elements send conflicting signals to LLMs and crawlers.","context":"This task is triggered whenever the number of '<h1>' tags is not equal to 1 (0 or >1). It is especially critical on landing pages, product pages, and articles.","recs":{"unique":"Ensure each URL has exactly one '<h1>'. Remove extra '<h1>' tags and use '<h2>'/'<h3>' for subtopics instead.","reflectTopic":"Make the '<h1>' text accurately reflect the main topic in natural language, including key entities or the primary keyword."}},"hierarchy":{"title":"Heading structure skips levels","description":"Heading levels on your page skip steps (e.g. '<h2>' directly followed by '<h4>'), which breaks the semantic document outline. LLMs lose a clear hierarchy of how subtopics relate to main topics.","context":"This task is triggered when the heading sequence jumps by more than one level (e.g. h2 → h4/h5), indicating a structural issue.","recs":{"sequence":"Follow a clean structure: '<h1>' for the main topic, '<h2>' for main sections, '<h3>' for subsections, etc. without jumps.","avoidSkipping":"When introducing new sections, increase heading levels only by one (h2 → h3 → h4). Use CSS for visual styling, not incorrect heading levels."}}},"html":{"p":{"title":"Text not wrapped in '<p>' tags","description":"A significant part of the textual content is not enclosed in '<p>' elements but only in generic containers like '<div>' or '<span>'. LLMs then struggle to detect paragraph boundaries and coherent sense units.","context":"This task is triggered when the ratio between text blocks and '<p>' tags is atypically low (lots of text but very few '<p>' elements).","recs":{"usePTags":"Wrap each real paragraph in a '<p>' element instead of putting text directly into '<div>' or '<span>'.","avoidDivSpan":"Use '<div>'/'<span>' mainly for layout or styling, not for semantic paragraph structure. This helps LLMs analyze text logic more effectively."}},"grouping":{"title":"Missing semantic grouping","description":"Content sections (e.g. features, benefits, testimonials) are not grouped using semantic containers like '<section>' or '<article>'. LLMs see only a flat structure instead of clear topic blocks.","context":"This task is triggered when many headings and content blocks exist but there are no '<section>' or '<article>' elements in the markup.","recs":{"section":"Use '<section>' elements to group related content (e.g. \"Features\", \"Customer Stories\", \"FAQ\"), optionally with aria-labels.","article":"For standalone content like blog posts or news entries, wrap the content in '<article>' so LLMs can treat it as an independent document."}},"nav":{"title":"Missing semantic '<nav>' structure","description":"Navigation exists but is not wrapped in a '<nav>' element. Without '<nav>', crawlers, LLMs, and screen readers cannot clearly distinguish menu areas from regular in-content links.","context":"This task is triggered when typical navigation patterns (logo + main menu, burger menu, footer menu) are detected, but no '<nav>' element is present in the DOM.","recs":{"wrap":"Wrap your main navigation in a '<nav>' element, e.g. '<nav aria-label=\"Main navigation\">'…'</nav>', so crawlers and LLMs can classify it as navigation.","a11y":"If you have multiple menus (header, footer, language switcher), use separate '<nav>' elements with meaningful aria-labels to improve structure and accessibility."}},"lists":{"title":"Unstructured list items","description":"You have '<li>' elements that are not nested inside a '<ul>' or '<ol>'. This violates HTML semantics and makes it harder for LLMs to recognize lists as grouped items.","context":"This task is triggered when '<li>' tags appear in the DOM without an enclosing '<ul>' or '<ol>', often due to CSS-based layout hacks.","recs":{"useUlOl":"Always wrap list items in '<ul>' (unordered) or '<ol>' (ordered) containers.","noLiOutside":"Refactor '<li>' elements outside of lists; use '<div>' or '<p>' if the items are not logically part of a list."}},"tables":{"title":"Table-like data without '<table>'","description":"Tabular structures (rows/columns) were detected but without proper '<table>', '<tr>', '<th>', and '<td>' markup. LLMs cannot reliably interpret the data as a table.","context":"This task is triggered when layout patterns suggest a table built with '<div>' columns/rows but no semantic '<table>' HTML is used.","recs":{"structure":"Use '<table>' as a container and structure rows with '<tr>' and cells with '<th>' (headers) and '<td>' (data).","headerCell":"Mark header cells explicitly with '<th scope=\"col\">' or '<th scope=\"row\">' so LLMs and screen readers can understand relationships between headers and data cells."}},"emphasis":{"title":"Missing semantic emphasis tags","description":"No '<strong>' or '<em>' tags were found. Without these, LLMs cannot see which statements are particularly important or emphasised, especially when emphasis is only applied via CSS.","context":"This task is triggered when there is a lot of body text but no semantic emphasis tags, indicating that emphasis is likely only visual.","recs":{"strongEm":"Use '<strong>' to mark key statements and '<em>' for emphasis or contrast in text. This signals semantic importance to LLMs.","avoidBI":"Avoid using '<b>' and '<i>' purely for styling when semantic emphasis is intended. Prefer '<strong>'/'<em>' and style them via CSS."}}},"images":{"altMissing":{"title":"Missing alt attributes","description":"Detected {count} image(s) without alt attributes. Without alt text, screen readers and LLMs cannot interpret the content of images – they effectively remain invisible to AI search.","context":"This task is triggered when '<img>' elements are found without an alt attribute, except for purely decorative images with role=\"presentation\" or aria-hidden=\"true\".","recs":{"useAlt":"Provide descriptive alt=\"…\" text for all content-bearing images that explains the subject and purpose (e.g. \"Product photo: {productName} front view\").","skipDecorative":"Only leave alt empty (alt=\"\") for purely decorative images and optionally mark them with role=\"presentation\" so LLMs know they can be ignored."}},"altPoor":{"title":"Low-quality alt text","description":"Detected {count} image(s) with generic or unhelpful alt text (e.g. \"image\", \"photo\", \"screenshot\"). Such alt text does not provide any usable information to LLMs.","context":"This task is triggered when alt attributes consist only of generic terms or file names and add no semantic value.","recs":{"describePurpose":"Write alt text that summarizes the information content of the image: what is visible, and what role does the image play in the page context?","avoidVague":"Avoid vague labels like \"image\", \"photo\", or raw file names. Use descriptive language that supports LLMs in understanding context."}},"tagUsage":{"title":"Images should use '<img>' tags","description":"No '<img>' elements were found, but CSS background-image is used. Background images are hard or impossible to interpret for LLMs and many tools.","context":"This task is triggered when background-image is used in CSS but there are no corresponding '<img>' tags in the HTML, especially for meaningful visuals like hero, product, or author images.","recs":{"useImgTag":"Use explicit '<img>' elements with src, alt, and optional width/height for all content-bearing images. Reserve background-image for purely decorative backgrounds.","useBgOnlyDecorative":"If you continue to use CSS backgrounds, ensure that all important information is also available as HTML/text or via a proper '<img>' tag."}},"responsive":{"title":"Missing Responsive Images","description":"Images were detected without a srcset attribute. Without responsive sources, the browser must always download a single fixed image size, which can be unnecessarily large on mobile or too small on high-resolution screens. This hurts performance, Core Web Vitals and, indirectly, how AI systems evaluate page quality.","context":"This task is triggered when '<img>' elements are found that use only src without any srcset/sizes attributes. For AI search and LLMs, performance and UX signals (especially on mobile) increasingly influence which pages are surfaced as high-quality answers. Non-responsive images increase load time, data usage and layout instability, which can negatively affect these quality metrics.","recs":{"addSrcset":"Provide multiple image resolutions via srcset on important images, e.g. '<img src=\"hero-800.jpg\" srcset=\"hero-400.jpg 400w, hero-800.jpg 800w, hero-1600.jpg 1600w\" alt=\"…\">' so the browser can choose the most appropriate asset.","includeSizes":"Always include a sizes attribute that reflects your layout (e.g. sizes=\"(max-width: 768px) 100vw, 50vw\") so the browser can pick the optimal candidate from srcset instead of guessing.","optimizeKeyImages":"Start with above-the-fold and LCP-relevant images (hero, key product visuals). Ensure they have responsive srcset/sizes definitions and are properly compressed (WebP/AVIF where supported).","setDimensions":"Include explicit width and height (or CSS aspect-ratio) for responsive images to prevent layout shift and give the browser enough information to reserve space before the image loads.","avoidOverserving":"Avoid serving a single 2000px-wide image to all devices. Use srcset/sizes to prevent overserving on mobile connections and to improve perceived speed for AI-driven performance scoring."}},"cssBackground":{"title":"Images Hidden in CSS","description":"Important visual content is implemented via CSS background-image instead of '<img>' tags. AI crawlers and accessibility tools primarily parse the DOM, not CSS backgrounds, so these images are effectively invisible for indexing and semantic understanding.","context":"This task is triggered when background-image URLs are detected on elements that appear to contain primary content (e.g. hero sections, key product visuals, explainer graphics) but no corresponding '<img>' tag is present in the markup. For LLMs and search engines, only content exposed in the DOM with proper semantics (img + alt, picture, figure) can be reliably interpreted, associated with entities, and reused in rich results.","recs":{"useImgTag":"Render content-relevant images as standard '<img>' (or '<picture>') elements in the HTML, and reserve CSS background-image primarily for decorative or purely stylistic visuals.","addAltText":"When converting background images to '<img>', add descriptive alt text that explains the purpose of the image (not just \"background\" or \"image\"). This helps both AI systems and assistive technologies.","combineWithFigure":"For key illustrations or diagrams, wrap the '<img>' in a '<figure>' with an optional '<figcaption>' to give AI crawlers additional context about what the image shows.","keepDecorativeInCSS":"Keep truly decorative visuals (patterns, gradients, subtle textures) as CSS backgrounds with role=\"presentation\" or aria-hidden=\"true\" where appropriate, so crawlers focus on meaningful images.","ensureCrawlability":"Avoid using background images for critical content in sliders, hero banners or product galleries. If the image conveys information a user needs, expose it in the DOM as an '<img>' so AI crawlers can \"see\" it."}}},"htmlSemantics":{"semanticGrouping":{"title":"Missing Semantic Structure ('<article>'/'<section>')","description":"No '<article>' or '<section>' tags were found. AI models and search engines rely on these semantic containers to understand which parts of the DOM form the main content, which sections belong together, and how topics are structured across the page. Without them, your page looks like a flat collection of '<div>' blocks with little inherent meaning.","context":"This task is triggered when the page contains substantial text content (multiple headings and paragraphs), but no '<article>' or '<section>' tags are present in the HTML. In modern HTML, '<article>' and '<section>' are key signals for content hierarchy: they tell LLMs which parts are standalone pieces (articles, blog posts, product descriptions) and which are thematic subsections. Without this semantic scaffolding, AI crawlers must guess where one topic ends and another begins, which can dilute topical relevance and snippet extraction quality.","recs":{"wrapInArticle":"Wrap your main content (e.g. a blog post, detailed product description or long-form guide) in a single '<article>' element to signal a self-contained composition, e.g. '<article>…main content…</article>'.","useSectionForChapters":"Use '<section>' tags to group thematically related content blocks inside the article (e.g. '<section>Introduction</section>', '<section>Use Cases</section>', '<section>FAQ</section>'). Each '<section>' should represent a logical chapter or major segment.","pairWithHeadings":"Ensure each '<section>' starts with an appropriate heading ('<h2>' or '<h3>'). This combination of '<section>' + heading gives AI models a strong structural signal for topic hierarchy.","separateAncillaryContent":"Use distinct '<section>' or '<aside>' containers for secondary content such as sidebars, related articles, or CTAs so that AI systems can distinguish main narrative from supporting blocks.","avoidDivOnlyLayouts":"Refactor purely '<div>'-based layouts by replacing structural wrappers with semantic elements ('<header>', '<main>', '<article>', '<section>', '<footer>'). This reduces noise and helps AI parsers interpret the DOM more like a document than an app shell."}},"navTag":{"title":"Missing Semantic Navigation ('<nav>')","description":"Primary navigation links are not wrapped in a '<nav>' element. Without '<nav>', AI crawlers and assistive technologies cannot clearly separate global navigation from the unique page content, making it harder to understand your site architecture and reduce boilerplate noise.","context":"This task is triggered when clusters of internal links (e.g. main menu, footer menu) are detected but not contained within a '<nav>' element. For LLMs and search engines, '<nav>' is a strong signal that a block of links represents navigation rather than body content. This helps them de-emphasise boilerplate menus when analysing page topics and focus on the central content that should rank and be cited.","recs":{"useNavForMenu":"Wrap your primary site-wide menu (usually in the header) in a '<nav>' element, e.g. '<nav class=\"main-nav\">'…menu links…'</nav>'. Do the same for structured footer link groups that act as secondary navigation.","addAriaLabel":"Add an aria-label to distinguish multiple navigation regions, e.g. '<nav aria-label=\"Main menu\">' in the header and '<nav aria-label=\"Footer links\">' in the footer. This helps both screen readers and AI systems interpret their roles.","avoidOverWrapping":"Do not wrap the entire page or unrelated content in '<nav>'. Limit '<nav>' to genuine navigation structures (menus, link lists, breadcrumbs) to keep semantics clean.","structureMenus":"Use '<ul>'/'<li>' inside '<nav>' for menus instead of a flat sequence of '<a>' tags. This creates a predictable, structured pattern that crawlers recognise as navigation.","separateFromContent":"Ensure that main content is placed in '<main>' or '<article>', distinct from '<nav>'. This clear separation makes it easier for AI to ignore navigation noise when extracting topical content."}},"semanticEmphasis":{"title":"Non-Semantic Emphasis Tags","description":"The page uses '<b>' or '<i>' tags for emphasis. These tags are purely visual and do not convey meaning to AI systems. Semantic emphasis tags like '<strong>' and '<em>' signal which words or phrases carry extra importance or change the interpretation of a sentence.","context":"This task is triggered when '<b>' or '<i>' elements are detected in text content while '<strong>' and '<em>' are underused or missing. For LLMs and search engines, semantic emphasis is a valuable hint: '<strong>' indicates importance (e.g. key claims, warnings, core benefits), and '<em>' indicates stress emphasis that can change meaning. Relying only on '<b>'/'<i>' removes this semantic layer, making it harder for AI to identify what truly matters in your copy.","recs":{"useStrong":"Replace '<b>' used for emphasis with '<strong>' when you want to mark key statements (e.g. main benefits, warnings, guarantees). Example: '<strong>30-day money-back guarantee</strong>' instead of '<b>30-day money-back guarantee</b>'.","useEm":"Use '<em>' when you want to stress a word or phrase that changes the nuance or focus of a sentence (e.g. \"We only ship to '<em>verified</em>' business addresses\").","keepBIForStylingOnly":"If you must keep '<b>' or '<i>' for icon fonts or purely stylistic purposes (e.g. italicised brand names), ensure they are not your primary mechanism for emphasising meaningfully important text.","highlightKeyClaims":"Review your most important claims (pricing, guarantees, limitations) and wrap them in '<strong>' so AI systems can better recognise them as central statements of your offer.","avoidOverEmphasis":"Use '<strong>' and '<em>' sparingly and intentionally. Overusing emphasis tags dilutes their semantic value and makes it harder for AI to distinguish truly important content from visual styling."}}},"internalLinking":{"none":{"title":"Missing internal linking","description":"Too few or no internal links were detected. Without internal links, crawlers and LLMs cannot easily understand your information architecture and topic clusters.","context":"This task is triggered when the number of distinct internal paths is below a threshold (e.g. < 5), indicating the page is isolated and poorly connected to the rest of the site.","recs":{"linkRelated":"Add links from this page to related topics, category pages, or pillar content using standard '<a href=\"/path\">' links.","makeCrawlable":"Ensure internal links are crawlable and not hidden behind JavaScript-only interactions or non-standard URL patterns."}},"pillarCluster":{"title":"Missing pillar-cluster linking","description":"There are too few connections between pillar pages and detailed cluster articles. LLMs recognize topical authority much better when this structure is clearly expressed.","context":"This task is triggered when blog/knowledge/category pages have too few links to related detail pages (cluster content) or vice versa.","recs":{"linkToPillar":"Ensure that all cluster articles link back to their pillar (main topic) pages, using descriptive anchor text such as \"Overview: {topic}\".","linkToCluster":"From pillar pages, link out to the most important cluster articles (e.g. \"Further articles on {topic}\") and structure them as lists or a table of contents.","useAnchorText":"Use descriptive anchor text that reflects topic and intent rather than generic labels like \"click here\". This helps LLMs understand the topic graph."}},"descriptiveAnchorText":{"title":"Generic Anchor Text Detected","description":"Found {count} internal link(s) with generic anchor text (e.g. \"click here\", \"read more\"). Generic anchors provide almost no topical signal to AI systems or search engines. Descriptive, keyword-rich anchor text helps models understand what the linked page is about and how it fits into your overall site architecture.","context":"This task is triggered when '<a>' elements are detected whose innerText matches common generic patterns (e.g. \"click here\", \"read more\", \"more\", \"here\") or very short, contextless labels. For LLMs and modern search engines, anchor text is a key relevance signal: it describes the destination URL in natural language and helps AI understand entity relationships, topic clusters and user journeys. Overuse of generic anchors weakens internal linking, makes crawl paths semantically opaque and reduces the chance that linked pages are recognised as strong candidates for specific queries.","recs":{"useDescriptiveText":"Replace generic phrases with descriptive, human-readable anchor text that explains the destination (e.g. \"View AI-SEO pricing\" instead of \"click here\"). Make the anchor text understandable even out of context.","includeKeywords":"Include relevant keywords and entities in the anchor text that reflect the linked page's main topic (e.g. \"AI-SEO audit for e-commerce\" linking to your audit page). This helps AI connect the link target to specific intents and topics.","avoidGenericPhrases":"Avoid anchors like \"click here\", \"read more\", \"more\", \"here\", \"learn more\" without context. If you must use them, at least combine them with descriptive text (e.g. \"Read more about our AI-SEO methodology\").","matchPageIntent":"Align anchor text with the primary intent of the target URL (e.g. use verbs like \"Download\", \"Compare\", \"Calculate\" for tools or downloads, and topic-focused phrases for guides or blog posts). This improves how AI maps links to user tasks.","keepAnchorsConcise":"Keep anchor text concise but specific (typically 2–8 words). Avoid stuffing entire sentences or keyword lists into a single anchor, which can look spammy and reduce clarity for both users and AI.","reviewKeyPaths":"Audit key internal paths (e.g. homepage → product, product → pricing, blog → product) and ensure they use strong descriptive anchor text, as these links carry disproportionate weight for both AI and traditional search."}}},"internationalization":{"langAttr":{"title":"Missing or incorrect '<html lang>' attribute","description":"The '<html>' element does not contain a valid lang attribute (e.g. '<html lang=\"en-US\">'). Without a clean BCP-47 language tag, search engines and LLMs can only guess language and target region heuristically.","context":"This task is triggered when the root element has no lang attribute, uses a placeholder value (e.g. lang=\"en\" on a non-English page), or specifies an invalid code. LLMs combine automatic language detection with the lang attribute; if this signal is missing or wrong, misclassification becomes more likely.","recs":{"setCorrectLang":"Set a valid BCP-47 language tag on the root element, e.g. '<html lang=\"en\">' for generic English, '<html lang=\"en-US\">' for US English, '<html lang=\"de-DE\">' for German (Germany).","alignLangWithContent":"Ensure the lang attribute matches the actual primary content language. Avoid lang=\"en\" on purely German pages, for example.","useRegionCodesIfRelevant":"Use language-region variants (e.g. \"en-GB\", \"fr-CA\") when you explicitly target specific markets and want LLMs to respect those distinctions.","keepLangConsistent":"Keep the lang attribute consistent across all templates and layouts of the same language, so crawlers and LLMs do not receive conflicting signals.","avoidMultipleHtmlTags":"Ensure there is only one '<html>' element with a clearly defined lang attribute and no nested or duplicated HTML roots."}},"hreflang":{"title":"Missing or incomplete hreflang tags","description":"No proper '<link rel=\"alternate\" hreflang=\"…\" href=\"…\">' tags were found for multilingual or country-specific variants. Without hreflang, search engines and LLMs cannot reliably connect language and regional versions of the same content.","context":"This task is triggered when multiple language or locale versions of a page exist (e.g. /en/, /de/, /fr/ or country-specific domains), but there is no consistent hreflang linking between these URLs in the '<head>'. For LLMs, this makes it harder to choose the correct language/region version when generating answers.","recs":{"defineLanguageMatrix":"Create a complete matrix of all language and country variants (e.g. en-US, de-DE, fr-FR) and assign a canonical URL to each variant.","addHreflangLinks":"Add '<link rel=\"alternate\" hreflang=\"xx-YY\" href=\"https://example.com/path\">' tags for each variant in the '<head>'. Each URL should reference all variants including itself.","useXDefault":"Add an x-default entry for a neutral default URL, e.g. '<link rel=\"alternate\" hreflang=\"x-default\" href=\"https://example.com/\">' if you have a global landing page.","keepCodesValid":"Use valid BCP-47 codes (e.g. \"en-GB\", not \"en_GB\" or custom codes). Do not mix language and region codes arbitrarily.","syncWithSitemaps":"Optionally mirror the hreflang structure in XML sitemaps so crawlers and LLMs see language relationships both in HTML and in the sitemap."}}},"structuredData":{"articleProps":{"title":"Incomplete article schema properties","description":"Your Article or BlogPosting schema is missing key properties such as headline, datePublished, or author. LLMs then see less of the publishing context and treat the content more like generic text.","context":"This task is triggered when a @type \"Article\" or \"BlogPosting\" JSON-LD block exists but core fields like headline, datePublished, author, description, or mainEntityOfPage are missing.","recs":{"addHeadline":"Set a descriptive \"headline\" in the Article schema that is consistent with the visible '<h1>' title.","addDate":"Populate \"datePublished\" (and optionally \"dateModified\") with ISO 8601 dates that match visible dates and meta tags.","addAuthor":"Add an \"author\" object with \"@type\": \"Person\" or \"Organization\" and at least a \"name\" and ideally a \"url\" to an author or team page."}},"productProps":{"title":"Incomplete product schema properties","description":"Your Product or Service schema is missing critical fields such as offers or brand. LLMs cannot properly understand price and offer context or compare products.","context":"This task is triggered when a @type \"Product\" or \"Service\" block exists but properties like offers, brand, name, description, image, or sku are missing or empty.","recs":{"addOffers":"Add an \"offers\" property with an Offer object that reflects visible price information (e.g. price, priceCurrency, availability).","addBrand":"Set a \"brand\" property with the brand name as text or as a dedicated Brand/Organization object.","completeProductCore":"Ensure that \"name\", \"description\", \"image\", and ideally an identifier (sku, gtin) are provided so LLMs can uniquely reference the product."}},"orgProps":{"title":"Incomplete organization schema properties","description":"Your Organization schema is missing recommended fields like logo or url. LLMs perceive your brand less clearly as a distinct entity.","context":"This task is triggered when a @type \"Organization\" block exists but core properties like name, url, logo, or sameAs are missing.","recs":{"addLogo":"Add a \"logo\" property with an absolute image URL (HTTPS) that represents your company logo.","addUrl":"Set a \"url\" property with the canonical homepage URL (e.g. \"https://example.com/\").","addSameAs":"Use \"sameAs\" to reference official social and profile pages (LinkedIn, X, GitHub, industry directories) so LLMs can connect your brand across domains."}},"faqProps":{"title":"Incomplete FAQPage schema properties","description":"Your FAQPage schema is missing a proper mainEntity list of Question and Answer objects. LLMs cannot reliably reuse your FAQs as structured Q&A snippets.","context":"This task is triggered when a @type \"FAQPage\" JSON-LD block exists but \"mainEntity\" is missing or contains no valid Question/Answer pairs.","recs":{"addMainEntity":"Build \"mainEntity\" as an array of Question objects, each containing an acceptedAnswer with an Answer object.","mirrorVisibleFAQ":"Ensure that the most important visible FAQ questions are mirrored in schema and that texts match the HTML content."}},"speakable":{"title":"Missing Speakable Schema","description":"No Speakable markup (schema.org SpeakableSpecification) was found on this page. Without it, AI assistants and voice interfaces (e.g. ChatGPT Voice, Google Assistant, Alexa-style systems) have no explicit hint which parts of your content are best suited to be read aloud as concise answers.","context":"This task is triggered when the page is identified as article-like content (e.g. Article, BlogPosting, NewsArticle) but the structured data contains no speakable property referring to a SpeakableSpecification object. For LLMs and voice search experiences, Speakable markup is a strong signal that marks specific sections (selectors) as the canonical, short answer they should read or quote. Without it, AI systems must guess which paragraphs are most suitable for spoken output, which can reduce the quality and consistency of voice answers.","recs":{"addSchema":"Extend your Article/NewsArticle/BlogPosting JSON-LD with a speakable property that points to a SpeakableSpecification object. For example: \"speakable\": { \"@type\": \"SpeakableSpecification\", \"cssSelector\": [\".article-intro\", \"h2#key-facts + p\"] }.","useCssSelector":"Use cssSelector in SpeakableSpecification to reference 1–3 short, well-written sections (intro paragraph, key facts, summary). Avoid marking the entire article as speakable.","keepTextConcise":"Ensure the selected speakable sections are concise and self-contained (typically 20–80 words each), written in clear, natural language suitable to be read aloud without additional context.","alignWithMainAnswer":"Choose speakable sections that directly answer the core question or describe the main topic of the page (e.g. definition, key benefits, short summary). This helps AI voice systems deliver precise answers.","validateSchema":"Validate the extended schema (including SpeakableSpecification) using a structured data testing tool or Schema Markup Validator to ensure the JSON-LD syntax and selectors are valid and parsable.","keepSelectorsStable":"Avoid tying cssSelector values to fragile class names that may change often. Use stable IDs or robust selector patterns so your speakable markup doesn't silently break during redesigns."}},"brokenJson":{"title":"Fix invalid JSON-LD schema","description":"Your page contains JSON-LD structured data that cannot be parsed due to syntax errors (e.g. missing commas, wrong quotes). LLMs and search engines will ignore this markup.","context":"This task is triggered when parsing '<script type=\"application/ld+json\">' blocks throws a JSON error.","recs":{"validate":"Validate your JSON-LD with tools like JSONLint or Google's Rich Results Test and fix all parse errors.","fixSyntax":"Ensure correct JSON syntax: double quotes for keys and strings, commas between properties, no comments or trailing commas."}},"missingTypes":{"title":"Missing relevant schema.org types","description":"For this page type, the expected schema.org @type values (e.g. \"Organization\", \"WebSite\", \"Article\", \"Product\", \"FAQPage\") are missing. Without appropriate types, search engines and LLMs cannot reliably classify the page as a homepage, product detail, knowledge article, FAQ, etc.","context":"This task is triggered when content and layout clearly indicate a specific page type (e.g. product page with price & CTA, article page with title, date & author, FAQ page with many Q&A blocks) but no corresponding schema.org @type exists in any JSON-LD block. For LLMs, these types are strong signals for whether a page should be treated as a product, knowledge source, FAQ, or organization reference.","recs":{"addOrgAndWebsite":"Ensure your domain exposes at least one combined Organization and WebSite schema, e.g. in a global JSON-LD block: { \"@context\": \"https://schema.org\", \"@type\": \"Organization\", ... } and { \"@context\": \"https://schema.org\", \"@type\": \"WebSite\", ... }.","mapTemplatesToTypes":"Define per template which schema.org types must be present: e.g. blog article → \"Article\" or \"BlogPosting\", product detail → \"Product\" or \"Service\", FAQ landing → \"FAQPage\".","useJsonLdInHead":"Implement structured data as JSON-LD in the '<head>' wherever possible. Keep reusable JSON-LD blocks per page type and only inject dynamic fields (name, description, url, image, offers, etc.).","fillKeyProperties":"Whenever you introduce a type (e.g. \"Product\"), always populate key properties: product.name, description, brand, image, offers.price, offers.priceCurrency, offers.availability. For \"Article\", headline, datePublished, author, and description are crucial.","keepTypesConsistent":"Use consistent @type values and property names for the same page type across all URLs so LLMs can learn stable patterns for your site."}},"missingProps":{"title":"Incomplete schema key fields","description":"Some schema.org blocks exist but miss important fields (e.g. name, description, url), so LLMs only see a fragmented representation of your entities.","context":"This task is triggered when structured data is present but core properties are empty, generic (\"Lorem ipsum\", \"Insert Description\"), or completely missing.","recs":{"completeFields":"Ensure all core entities (Organization, WebSite, Article, Product, FAQPage) have at least name, description, and url populated with real values.","avoidPlaceholders":"Remove placeholder texts like \"Insert Description Here\" or \"Dummy\" from schema and replace them with accurate, descriptive content that matches visible text."}},"missingOg":{"title":"Missing Open Graph tags","description":"The following OG tags are missing: {tags}. Without og:title, og:description, og:image, and og:url, many systems (social, chat, LLMs) lack clear preview information for your page.","context":"This task is triggered when the '<head>' is missing core '<meta property=\"og:*\">' tags on pages that are likely to be shared or referenced.","recs":{"addOgTags":"Add at least og:title, og:description, og:image, and og:url to the '<head>' using '<meta property=\"og:title\" content=\"…\" />' etc.","accurateValues":"Ensure OG values match the visible title, meta description, and canonical URL, and choose a compelling og:image (HTTPS, correct format, suitable dimensions)."}},"generalMissing":{"title":"Missing general schema markup","description":"No relevant schema.org types such as Organization, WebSite, Article, Product, or FAQPage were detected on this page. LLMs lack a structured layer for interpreting your content.","context":"This task is triggered when there is HTML content but no JSON-LD or Microdata markup with common schema.org types.","recs":{"addRelevantSchema":"Add appropriate schema.org types for each key page type (e.g. Organization + WebSite on homepage, Article/BlogPosting for blog posts, Product/Service for product pages, FAQPage for FAQ landings).","followGuidelines":"Use JSON-LD as the preferred format and follow schema.org and Google documentation on structured data and rich results."}},"robotsBlocked":{"title":"AI bots blocked by robots.txt","description":"Your robots.txt is blocking access for: {bots}. This prevents important AI crawlers from fully indexing your content. LLMs will then rely more on third-party sources instead of your site directly – you lose control over freshness, context, and brand messaging.","context":"This task is triggered when robots.txt contains Disallow rules for relevant AI and search bots (e.g. OAI-SearchBot, Bingbot, ClaudeBot or similar crawlers), especially for content-heavy sections (e.g. /blog, /products, /docs). For LLMs, this means less direct access to your content, lower AI search visibility, and higher dependency on external, possibly outdated sources.","recs":{"reviewRobots":"Systematically review robots.txt and identify all Disallow rules that affect AI-relevant bots or important content directories. Pay special attention to global rules such as \"User-agent: *\\nDisallow: /\".","defineAIPolicy":"Define a clear AI crawling strategy: which areas should AI bots explicitly be allowed to read (e.g. /blog, /knowledge, /products, /faq) and which areas must remain protected (e.g. /admin, /internal, staging domains)?","whitelistKeyBots":"Explicitly allow key AI and search bots for permitted areas, e.g.: \"User-agent: OAI-SearchBot\\nAllow: /\", \"User-agent: Bingbot\\nAllow: /\" instead of blanket Disallow rules that treat all bots the same.","avoidOverBlocking":"Avoid overly aggressive blocking such as domain-wide Disallow or Disallow for important content directories. Use targeted Disallow rules only for genuinely sensitive paths (e.g. /wp-admin/, /checkout/, /user-data/).","syncWithSitemaps":"Make sure that content relevant to AI search is both allowed in robots.txt and referenced in XML sitemaps so AI crawlers can discover important pages quickly and reliably.","documentDecisions":"Document which bots are allowed and which areas are blocked (and why) so future changes to robots.txt do not accidentally destroy your AI visibility."}}},"metaTags":{"title":{"missing":{"title":"Missing Meta Titles","description":"The following page(s) are missing title tags","context":"This task is triggered when a document lacks a '<title>' element or the element is empty/whitespace. The '<title>' tag is one of the strongest on-page signals for search engines and LLMs to understand what a URL is about. It is also what users see in browser tabs and often in search result snippets. Pages without a proper title are harder to map to queries, topics and entities.","recs":{"addTitle":"Add a unique, descriptive '<title>' element to each HTML document, e.g. '<title>AI-SEO Audit for E-Commerce Shops

15:["$","$L17",null,{"formats":"$undefined","locale":"en","messages":{"HomePage":{"title":"Welcome to the Home Page","description":"This is the home page of our application.","signIn":"Sign in","signOut":"Sign out","subscribe":"Subscribe"},"LocaleSwitcher":{"de":"Deutsch","en":"English","label":"Language"},"Table":{"tasksOverview":"Tasks Overview","taskDescription":"Manage and track all your AI-SEO analysis tasks","shared":{"description":"Shared description for all tasks","context":"Shared context for all tasks","recommendations":"Shared recommendations for all tasks"},"filters":{"searchPlaceholder":"Search tasks...","status":"Status","statusLabel":"Filter by Status","category":"Category","categoryLabel":"Filter by Category","priority":"Priority","priorityLabel":"Filter by Priority","clear":"Clear Filters"},"columns":{"task":"Task","category":"Category","priority":"Priority","status":"Status","dueDate":"Due Date","noDueDate":"No due date","actions":"Actions","affectedPages":"{count} page{count, plural, one {} other {s}} affected","createdAt":"Created At"},"categories":{"altText":"Alt-Text Tasks","schemaMarkup":"Schema Markup Tasks","metaData":"Meta Data Tasks","content":"Content Tasks","technicalSeo":"Technical AI-SEO","performance":"Performance Tasks"},"priorities":{"low":"Low","medium":"Medium","high":"High","critical":"Critical"},"stats":{"total":"{count} Total Tasks","open":"{count} Open","completed":"{count} Completed","overdue":"{count} Overdue"},"statuses":{"open":"Open","completed":"Completed"},"actions":{"confirmDeleteTitle":"Confirm Delete","confirmDeleteDescription":"Are you sure you want to delete this task? This action cannot be undone.","cancel":"Cancel","delete":"Delete","deleteSuccess":"Task deleted successfully.","deleteError":"Failed to delete task.","complete":"Complete","completeSuccess":"Task marked as completed.","completeError":"Failed to mark task as completed.","confirmCompleteTitle":"Confirm Completion","confirmCompleteDescription":"Are you sure you want to mark this task as complete?","processing":"Processing..."},"pagination":{"showing":"Showing {current} of {total} task(s)","previous":"Previous","next":"Next"},"TaskDetail":{"title":"Task Details","description":"Description","context":"Context","recommendations":"Recommendations","affectedPages":"Affected Pages","taskStatus":"Task Status","pending":"Pending","completed":"Completed","dueDate":"Due by","markComplete":"Mark as Complete","codeExample":"Code Example","noCodeExample":"// No code example available for this task"},"empty":"No results.","perfectScore":{"title":"🎉 Perfect AI-SEO Score!","description":"Congratulations! Your website has achieved a perfect AI-SEO score. No optimization tasks are needed at this time.","subtitle":"Your site is well-optimized and follows all AI-SEO best practices we analyzed."},"tasks":{"contentQuality":{"entityMentions":{"title":"Missing Brand or Product Mentions","description":"The brand or product name is missing from the '' tag, the main heading ('<h1>'), or the first paragraph. This weakens the signal about which entity the page is primarily about and makes it harder for LLMs to connect the page to your brand or product.","context":"This task is triggered when the configured brand or product name does not appear in the '<title>', '<h1>', or the first text block of the page, especially on critical templates such as homepage, product, about, contact, or careers pages. For LLMs, this reduces entity clarity and brand presence in answers.","recs":{"titleMention":"Include your brand and/or product explicitly in the '<title>' tag (e.g. \"{brand} – {product} for {useCase}\"). This gives crawlers and LLMs a clear entity signal.","firstParagraphMention":"Mention the brand/product in the first paragraph in natural language (e.g. \"{brand} is…\") so LLMs interpret it as a stable entity reference."}},"keyphrases":{"title":"Insufficient topical depth and semantic coverage","description":"Key target phrases {phrases} are underused or missing. LLMs rely on semantic density (topic clusters, synonyms, variations) to understand relevance and authority. Without these signals, your page is less likely to be treated as an authoritative source for this topic.","context":"This task is triggered when the target keyphrases derived from project context and page type are not found or only minimally present in '<title>', '<h1>', the first paragraph, and the early body text. The check is tolerant to light variations (plural/singular, hyphen vs. space).","recs":{"includePhrases":"Integrate the target terms {phrases} naturally into headings ('<h2>', '<h3>') and body copy. Build meaningful topic clusters instead of mentioning each phrase only once.","matchIntent":"Extend your content to cover typical user intents (e.g. \"What is…?\", \"How does… work?\", \"Pros/cons\") using synonyms and long-tail variations. This helps LLMs classify the page as a comprehensive resource."}},"tableOfContents":{"title":"Missing Table of Contents","description":"This long-form content (>1500 words) lacks a Table of Contents with anchor links, which makes it harder for users and AI systems to understand the structure and jump to specific sections.","context":"This task is triggered when the estimated word count exceeds ~1500 words, multiple subheadings ('<h2>'/'<h3>') are present, but no ToC pattern is detected near the top of the page (e.g. a \"Contents\" / \"Table of Contents\" block with internal #anchor links). For LLMs, a clear ToC improves section detection and deep-linking to specific subtopics inside a long article.","recs":{"addTableOfContents":"Add a prominent Table of Contents near the beginning of the article (typically right after the '<h1>') that lists the main '<h2>'/'<h3>' sections.","useAnchorLinks":"Use in-page jump links (e.g. '<a href=\"#section-intro\">Introduction</a>') and matching IDs on headings (e.g. '<h2 id=\"section-intro\">…</h2>') so users and AI systems can jump directly to specific sections.","keepToCInHtml":"Implement the ToC as real HTML (e.g. '<nav aria-label=\"Table of contents\"><ul>…</ul></nav>') rather than only visually in the template, so crawlers and LLMs can reliably detect the structure."}},"definitiveAnswer":{"title":"Missing definitive answer after question headings","description":"Headings formulated as questions are not directly followed by a concise answer paragraph. This lowers the chance of being used as a direct answer (e.g. Featured Snippet or LLM short answer).","context":"This task is triggered when headings ending with a question mark or containing typical question patterns (e.g. \"How…?\", \"What is…?\") are detected, but the immediately following paragraph is either missing or too long/indirect. LLMs prefer short, precise answer snippets immediately after the question and use the following text for deeper explanation.","recs":{"addAnswerAfterQuestion":"Place a clear, standalone answer paragraph (roughly 20–80 words) immediately after each question heading before going into more detail.","keepAnswersConcise":"Avoid fluff, disclaimers, or long introductions in the first 1–2 sentences after a question. Start with the actual answer; examples, background and nuance can follow afterwards.","reuseForFAQ":"Apply this pattern (question heading + short direct answer paragraph) to FAQ-style sections as well to increase your chances of being surfaced as a direct answer in AI systems."}},"urlStructure":{"title":"Non-semantic URL structure","description":"The URL contains underscores, uppercase letters, excessive depth, or mostly technical fragments (IDs, parameters). Such URLs are harder to read for users and provide weaker topical signals to LLMs.","context":"This task is triggered when the path includes underscores (\"_\"), uppercase letters, more than about three directory levels, or primarily technical patterns (e.g. /post?id=1234 or /category/1234-abc/). Clean, semantic slugs help LLMs infer the main topic and entities of a page directly from the URL.","recs":{"useHyphens":"Use lowercase letters and hyphens instead of underscores (e.g. /ai-seo-check/ instead of /AI_SEO_Check/). This improves readability and consistency.","keepFlat":"Keep the URL depth as flat as reasonably possible (ideally no more than 3 levels deep, e.g. /blog/ai-seo-basics/) instead of deeply nested paths.","useSemanticSlugs":"Use human-readable, topic-focused slugs that include key terms and entities (e.g. /products/ai-seo-plugin/ instead of /products/item-123/). Avoid unnecessary parameters and opaque IDs wherever possible."}}},"eta":{"authorityLinks":{"title":"Missing trust-by-association signals","description":"No external links to trusted domains (e.g. .gov, .edu, official organizations) were found. Such references signal to LLMs that your content is well-researched and embedded in a reliable information network.","context":"This task is primarily triggered on knowledge-type pages (e.g. blog, case studies) when no outbound links to authoritative domains are present. For LLMs, this weakens the impression that your content is well-supported and citable.","recs":{"includeTrustedSources":"When you cite facts, statistics, or studies, link to original, reputable sources using standard '<a href=\"…\">' links in the body content.","useAuthoritativeDomains":"Prefer links to highly trusted domains (e.g. .gov, .edu, reputable industry bodies), as these create strong trust-by-association signals for LLMs."}},"authorBio":{"title":"Missing author bylines or bios","description":"No clear author attribution (byline) or structured author information (meta tag, schema, author block) was found. LLMs score content with identifiable experts higher, especially for advisory or explanatory topics.","context":"This task is triggered when article-like pages (e.g. blog, case study) lack any author signals – no '<meta name=\"author\">', no schema.org author property, and no visible byline near the article.","recs":{"addAuthorNearContent":"Add a visible byline close to the title or introduction (e.g. '<p class=\"author\">By {name}</p>') using clear patterns like \"By\" or \"Von\".","includeBioWithCreds":"Add a short author bio with role, expertise, and optionally a link to a profile page (e.g. /team/{author}) and mirror it in Article schema (\"author\": { \"@type\": \"Person\", \"name\": \"…\" })."}},"trustSignals":{"title":"Missing experience or trust signals","description":"No clear trust signals such as client logos, testimonials, reviews, certifications, or case studies were detected. LLMs factor these into decisions about which providers or solutions to recommend.","context":"This task is triggered mainly on product, service, and about pages when no visual or textual evidence of real clients, projects, or awards is present and no review/rating schema can be found.","recs":{"includeSocialProof":"Add client logos, testimonials, review snippets, or award badges to your HTML and describe them in text (e.g. \"Awarded by…\").","linkToCaseStudies":"Link to dedicated case study or reference pages using descriptive anchors such as \"Case Study: {client}\" so LLMs can follow those relationships."}},"footerLinks":{"title":"Missing About or Contact pages","description":"The page is missing visible or linked \"About\" or \"Contact\" pages via typical footer or header links. This weakens transparency and trust signals for both LLMs and users.","context":"This task is triggered when no internal links whose URL or anchor pattern suggests About/Contact/Imprint/Legal pages can be found in the footer or header. LLMs then have less evidence about who operates the website.","recs":{"addAboutAndContactLinks":"Add internal links in footer (and optionally header) to /about, /contact, /imprint, /privacy, /terms, etc., using clear link labels such as \"About\" or \"Contact\".","includeCompanyDetails":"Ensure these pages contain address, contact options (email, phone), and legal details, ideally supported by Organization schema."}},"schemaEnrichment":{"title":"Missing E-E-A-T Schema Properties","description":"Your Person or Organization schema is missing key properties that communicate experience, expertise, authority, and transparency to AI systems. Without fields like alumniOf, knowsAbout, hasCredential, or award, LLMs have fewer structured signals to understand why you should be treated as a trustworthy, expert source.","context":"This task is triggered when a Person or Organization JSON-LD block is present, but important E-E-A-T-related properties are missing. The checker looks for @type \"Person\" or \"Organization\" and then inspects fields like alumniOf, hasCredential, knowsAbout, award, sameAs, publishingPrinciples, and ownershipFundingInfo. For LLMs, these properties act as explicit, machine-readable proof of qualifications, specializations, and editorial standards – not just marketing claims in plain text.","recs":{"addAlumniOf":"Add an \"alumniOf\" property for Person entities to reflect educational background (e.g. university, business school). Use either a plain text string or a nested Organization object.","addHasCredential":"Use \"hasCredential\" to model degrees, certifications, or professional licenses (e.g. ISO auditor certification, medical license) as structured data instead of just mentioning them in prose.","addKnowsAbout":"Populate \"knowsAbout\" with specific topics and domains (e.g. \"AI-SEO\", \"pharmaceutical supply chain\"). Where possible, point to canonical identifiers such as Wikidata URLs to strengthen entity linking.","addAward":"Add an \"award\" property listing notable awards, rankings, or recognitions your brand or experts have received (e.g. industry prizes, \"Top 100\" listings).","addPublishingPrinciples":"Expose your editorial standards via the \"publishingPrinciples\" property, linking to a public page that describes your review, fact-checking, conflict-of-interest, and update policies.","addOwnershipFundingInfo":"Use \"ownershipFundingInfo\" to disclose ownership structure, investors, or funding sources. This helps AI systems evaluate potential biases and improves perceived transparency.","addSameAs":"Use \"sameAs\" to link to verified external profiles (e.g. LinkedIn, official social accounts, Crunchbase, Wikipedia). This strengthens entity resolution and cross-checking in LLM training data.","keepConsistent":"Ensure that the names, roles, and organizations in your schema match the names and roles used on the page and across your site (no conflicting job titles or brand names)."}},"firstPersonDensity":{"title":"Low Experience Signals (First-Person)","description":"This content type (e.g., blog post, review, case study) uses very little first-person language (\"I\", \"we\", \"our\"), even though the topic suggests real-world experience. LLMs increasingly look for explicit experience cues to distinguish hands-on expertise from pure summary or affiliate-style content.","context":"This task is triggered when the page is classified as experience-heavy content (blog/review/guide) but the ratio of first-person pronouns in the main body text stays below a defined threshold. The checker scans for patterns like \"I\", \"we\", \"our\", \"my\" (and equivalents in the page language). For LLMs and modern search systems, clear first-person signals combined with concrete details are an important part of the \"Experience\" in E-E-A-T.","recs":{"usePersonalLanguage":"Where appropriate, switch from purely generic phrasing to more personal language that shows a real human is speaking (e.g. \"In our tests…\", \"In my experience…\").","useFirstPersonLanguage":"Add first-person pronouns (I, we, my, our) in sections that describe tests, projects, or client work – but only where this reflects actual experience, not fabricated claims.","sharePersonalExperience":"Explicitly describe what you or your team did, saw, or measured (e.g. \"We implemented this on 12 client sites\" or \"I ran this setup for 3 months before…\") instead of just summarizing general advice.","addConcreteDetails":"Strengthen experience signals by adding concrete details such as time frames, tools, metrics, and context (e.g. \"using GA4\", \"in a clinical setting\", \"with Shopify stores\"). This helps LLMs differentiate lived experience from generic content.","stayAuthentic":"Avoid artificially stuffing first-person phrases. Focus on authentic, verifiable experience and keep tone consistent with your brand and legal/compliance requirements."}}},"faq":{"schemaMissing":{"title":"Missing programmatic FAQ understanding","description":"FAQ-like content was detected (questions & answers), but no schema.org/FAQPage markup is present. LLMs can only see these as plain text, not as structured Q&A units.","context":"This task is triggered when headings or patterns such as \"FAQ\" / \"Frequently asked questions\" are detected, but there is no @type \"FAQPage\" in any JSON-LD block.","recs":{"implementJsonLD":"Implement a FAQPage schema in JSON-LD format in the '<head>' or near the end of the '<body>', using \"@type\": \"FAQPage\" and a mainEntity array of Question/Answer objects.","ensureSyntax":"Use the correct structure: each question as { \"@type\": \"Question\", \"name\": \"…\", \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"…\" } }. Validate using Google's Rich Results Test."}},"schemaInvalid":{"title":"Invalid or Incomplete FAQPage Schema","description":"An FAQPage schema was detected, but it contains structural errors or is missing required properties. Broken JSON-LD is ignored by search engines and AI systems, so you lose all potential FAQ rich result and AI visibility benefits.","context":"This task is triggered when a JSON-LD block declares @type \"FAQPage\" but fails basic validation: for example, mainEntity is missing or not an array, Question/Answer objects are incomplete, required fields like \"name\" or \"acceptedAnswer\" are missing, or the JSON itself is syntactically invalid. LLMs and search engines will typically ignore such schemas completely rather than partially interpreting them.","recs":{"validateStructure":"Check that your FAQPage JSON-LD follows the structure faq: { \"@type\": \"FAQPage\", \"mainEntity\": [ { \"@type\": \"Question\", \"name\": \"…\", \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"…\" } } ] }. Ensure mainEntity is an array of Question objects with acceptedAnswer.","useValidator":"Always validate your final schema in tools like Schema Markup Validator, Rich Results Test, or Search Console before deploying. Fix all reported errors and critical warnings.","fixRequiredFields":"Ensure every Question has a \"name\" and every Answer has a \"text\" field. Avoid leaving placeholders like \"Lorem ipsum\" or \"TODO\" in production data.","avoidMixedTypes":"Do not mix multiple unrelated @type values inside the same JSON-LD block (e.g. FAQPage + Product). Use separate JSON-LD blocks per logical entity to avoid parsing issues.","keepJsonValid":"Make sure the JSON is syntactically valid: no trailing commas, correct quotes around keys and values, and properly escaped special characters (e.g. quotes in question text)."}},"missingTags":{"title":"Missing FAQ expand/collapse tags","description":"FAQ content was found, but it is not wrapped in semantic '<details>'/'<summary>' tags. This makes it harder for LLMs and assistive tech to identify question-answer blocks.","context":"This task is triggered when FAQ-style headings or Q&A structures are present, but there are no '<details>' elements in the HTML even though a collapsible FAQ UI is expected.","recs":{"wrapInDetails":"Wrap each question/answer pair in a '<details>' element with a '<summary>' for the question and a block element (e.g. '<p>') for the answer.","correctStructure":"Use a clean pattern such as '<details><summary>Question…</summary><div>Answer…</div></details>' to improve both UX and machine understanding."}},"unstructured":{"title":"Unstructured FAQ detected","description":"FAQ-like content was identified via pattern matching (e.g. question-form headings) but without semantic markup or FAQPage schema. LLMs can reuse this content less reliably as standalone Q&A snippets.","context":"This task is triggered when multiple question-like headings or Q&A patterns exist, but no '<details>'/'<summary>' and no schema.org/FAQPage markup are present in the DOM.","recs":{"useDetails":"Format question/answer pairs using '<details>'/'<summary>' or a consistent Q&A HTML pattern (e.g. '<h3>Question</h3><p>Answer</p>').","addFAQSchema":"Add a FAQPage JSON-LD schema that covers the most important visible Q&A pairs and validate it with Google's Rich Results Test."}}},"freshness":{"visibleDate":{"title":"Missing visible freshness signals","description":"No visible \"Published on\" or \"Last updated\" date was found. Without dates, LLMs and search engines cannot distinguish whether content is current or outdated.","context":"This task is triggered when no date pattern can be detected in the visible content near the article title, header, or meta area. It is especially relevant for news, blogs, and knowledge articles.","recs":{"displayDate":"Place a clearly visible \"Published on\" or \"Last updated\" date near the title or introduction, e.g. in a '<time>' element or a '<span class=\"post-date\">'…'</span>'.","placeNearTop":"Ensure the date is shown in the upper part of the page so LLMs and users can quickly assess content recency."}},"timeTag":{"title":"Missing machine-readable '<time>' tag with datetime","description":"A visible date was detected but is not marked up with a '<time>' element including a datetime attribute. LLMs and search engines cannot reliably parse date information without machine-readable markup.","context":"This task is triggered when a date format is detected in text but no matching '<time datetime=\"…\">' element is present in the HTML.","recs":{"wrapInTime":"Wrap all important dates in '<time>' tags, e.g. '<time datetime=\"2024-05-21\">May 21, 2024</time>'.","addDatetime":"Use the datetime attribute in ISO 8601 format (YYYY-MM-DD or with time) so machines can parse and compare dates robustly."}},"metaTag":{"title":"Missing last-modified meta tags","description":"No '<meta name=\"last-modified\">' or '<meta property=\"article:modified_time\">' tag was found. These tags give crawlers a direct hint about when a page was changed.","context":"This task is triggered when visible dates exist but there are no corresponding meta tags in the '<head>' that indicate modification timestamps.","recs":{"addMetaTag":"Add '<meta name=\"last-modified\" content=\"2024-05-21\" />' or '<meta property=\"article:modified_time\" content=\"2024-05-21T10:30:00+02:00\" />' to the '<head>'.","keepUpdated":"Update these meta values automatically whenever content changes, so LLMs always see accurate freshness information."}},"sitemapLastmod":{"title":"Missing '<lastmod>' in sitemap","description":"Your sitemap.xml is missing '<lastmod>' tags for URL entries. Without this, crawlers and LLMs cannot easily prioritize which pages are fresh and important.","context":"This task is triggered when a sitemap is present but '<url>' blocks do not contain '<lastmod>' tags or use implausible dates.","recs":{"addLastmodTags":"Add a '<lastmod>' tag to each '<url>' entry in sitemap.xml (e.g. '<lastmod>'2024-08-25'</lastmod>').","useISODate":"Use ISO 8601 dates and keep them in sync with actual content changes.","checkCMSSettings":"Configure your CMS or sitemap plugin to maintain '<lastmod>' values automatically instead of hard-coding them."}},"sitemapUrlLastmod":{"title":"Missing '<lastmod>' in Sitemap Entry","description":"This URL is listed in your sitemap.xml but its '<url>' entry does not contain a '<lastmod>' tag. Without this timestamp, search engines and AI crawlers have weaker signals about when this specific page was last updated and how fresh its content is compared to other URLs.","context":"This task is triggered when a matching '<loc>' entry for this URL is found in sitemap.xml but the corresponding '<lastmod>' tag is missing, empty, or not in a valid date format. For LLMs and modern search systems, per-URL '<lastmod>' timestamps help prioritise crawling, recency-sensitive answers, and AI search features that highlight up-to-date sources.","recs":{"addLastmodToEntry":"Add a '<lastmod>' tag inside the '<url>' block for this page in your sitemap.xml, for example: '<lastmod>'2025-01-15'</lastmod>'.","useISODateFormat":"Use a valid ISO 8601 date format (e.g. 2025-01-15 or 2025-01-15T10:30:00+00:00) to ensure all crawlers can parse the value correctly.","updateOnContentChange":"Update the '<lastmod>' value whenever you significantly modify the page content, not just on minor layout tweaks, so AI systems understand when substantive information changed.","alignWithPageSignals":"Keep the '<lastmod>' date consistent with other freshness signals (e.g. visible \"Last updated\" text, modified_time meta tags) to avoid conflicting signals about recency.","automateSitemapGeneration":"If possible, configure your CMS or sitemap generator plugin to automatically maintain '<lastmod>' values based on real content changes, reducing manual work and errors."}},"lastModifiedMeta":{"title":"Missing Last Modified Meta Tag","description":"No '<meta name=\"last-modified\">' or '<meta property=\"article:modified_time\">' tag was found in the '<head>' of this page. These meta tags provide machine-readable freshness signals that help search engines and AI systems understand when the content was last updated.","context":"This task is triggered when the page has indexable content but no last-modified style meta tags in the '<head>'. While server headers and sitemaps can also carry freshness information, explicit meta tags like name=\"last-modified\" or property=\"article:modified_time\" give LLMs and search engines a clear, per-page timestamp directly tied to the HTML document.","recs":{"addMetaTag":"Add either '<meta name=\"last-modified\" content=\"2025-01-15T10:30:00+00:00\">' or '<meta property=\"article:modified_time\" content=\"2025-01-15T10:30:00+00:00\">' to the '<head>' section of the page.","keepUpdated":"Ensure the meta value is updated whenever the main content changes (e.g. via your CMS or build pipeline) so AI systems don't treat outdated content as fresh.","useISODateTime":"Provide the timestamp in ISO 8601 format including time and timezone where possible (e.g. 2025-01-15T10:30:00+01:00) to avoid ambiguity.","syncWithSitemap":"Keep the meta modified time in sync with the '<lastmod>' value in sitemap.xml for this URL to avoid conflicting freshness signals.","avoidFakeFreshness":"Do not update these timestamps artificially without real content changes. AI systems and search engines may downgrade sites that appear to manipulate freshness signals."}}},"headerFooter":{"tags":{"title":"Missing semantic header/footer structure","description":"The page is missing semantic '<header>' and/or '<footer>' elements. Without them, crawlers and LLMs cannot clearly separate global navigation, branding, and footer from main content.","context":"This task is triggered when typical header and footer patterns (logo, navigation, legal links, copyright) are detected but not wrapped in '<header>' or '<footer>' elements.","recs":{"wrapHeader":"Wrap the global top section (logo, main navigation, main CTA) in a '<header>' element, e.g. '<header>'…'</header>'.","wrapFooter":"Use a '<footer>' element for legal links, contact info, and copyright, so LLMs can treat this as a trust and context block."}},"headerEntity":{"title":"Missing Header Branding","description":"The '<header>' tag exists, but it does not clearly expose your brand as a recognizable entity (no site name in a heading and no logo image with meaningful alt text). This weakens the primary branding signal that AI systems use to understand which organization is behind the content.","context":"This task is triggered when a '<header>' element is present but no strong branding elements can be detected: no '<h1>'/'<h2>' with a site or brand name, and no '<img>' logo in the header with alt text that matches the brand. For LLMs and search engines, a clearly branded header is a key cue to map the page to a specific Organization or WebSite entity, align it with your Organization schema, and distinguish your brand from other domains or resellers.","recs":{"addH1":"Add a heading element in the header (ideally '<h1>' on the homepage, '<h2>' or '<div>' with role=\"heading\" on subpages) that contains your brand or site name in a clean text form (e.g. \"GAISEO – AI-SEO Platform\").","addLogo":"Include a logo image inside the '<header>' wrapped in a link to the homepage (e.g. '<a href=\"/\">' '<img src=\"/logo.svg\" alt=\"Your Brand Name\">' '</a>'). Make sure the alt text clearly states the brand name, not just \"logo\".","matchBrandName":"Ensure that the brand name in the header text and logo alt attribute matches the name used in your Organization schema (JSON-LD) and across other pages. Consistent naming makes entity resolution easier for AI systems.","useSemanticContainer":"Keep your primary branding elements inside the '<header>' element (logo, brand name, main navigation). Avoid scattering branding across multiple unrelated containers, which makes structural parsing harder.","supportAccessibility":"Use aria-label or aria-labelledby on the '<header>' if needed (e.g. '<header aria-label=\"Main site header\">') and ensure that the logo link has a descriptive alt or aria-label, improving both accessibility and machine understanding.","avoidTextInImagesOnly":"Do not rely solely on text embedded in images for your brand name. Always provide a text node (heading or span) with the brand name so AI and screen readers can read it reliably."}},"schema":{"title":"Missing organization identity for AI systems","description":"No Organization schema was found in the JSON-LD blocks. Without @type \"Organization\", LLMs lack a strong signal about who stands behind the website.","context":"This task is triggered when there is no Organization schema on domain-level or key pages (e.g. homepage, about), or when the schema is present but missing core properties such as name/url/logo.","recs":{"addBlock":"Add a JSON-LD block with \"@type\": \"Organization\" to your homepage (usually in the '<head>') using \"@context\": \"https://schema.org\".","includeFields":"Fill important properties like name, url, logo, address, contactPoint, and sameAs (links to social profiles) so LLMs can anchor your brand as a stable entity."}},"transparency":{"title":"Incomplete footer transparency signals","description":"The footer is missing key transparency signals such as links to Contact, About, Imprint/Legal, Privacy, or an address and copyright. This makes risk assessment harder for LLMs.","context":"This task is triggered when the footer contains few or no legal/trust-related elements and no recognizable link texts or patterns that indicate such pages.","recs":{"addLegalLinks":"Include links like \"About\", \"Contact\", \"Imprint\", \"Privacy\", and \"Terms\" in the footer with clear labels.","showAddress":"Display a full company address and at least one working contact channel (email or phone).","showCopyright":"Add a visible copyright notice such as \"© {year} {brand}. All rights reserved.\" and keep the year up to date."}}},"technicalAiSeo":{"fetchpriority":{"title":"Missing LCP Prioritization","description":"No image on the page uses fetchpriority=\"high\". Without explicitly prioritising the Largest Contentful Paint (LCP) image, the browser may load it later than needed, slowing perceived performance for both users and AI-driven performance audits.","context":"This task is triggered when no '<img>' or '<link rel=\"preload\" as=\"image\">' element for the main hero/LCP image is using fetchpriority=\"high\". Modern browsers use this hint to load the most important above-the-fold image earlier in the critical path. Since Core Web Vitals (especially LCP) are a strong quality signal that AI systems factor into ranking and evaluation, missing fetchpriority on the hero image can lead to slower LCP and weaker performance scores.","recs":{"addToHero":"Identify the main above-the-fold hero image (the likely LCP element) and add fetchpriority=\"high\" to its '<img>' tag, e.g. '<img src=\"hero.jpg\" fetchpriority=\"high\" ...>'.","combineWithPreload":"For critical hero images, consider combining fetchpriority=\"high\" with '<link rel=\"preload\" as=\"image\" href=\"/path/hero.jpg\">' in the '<head>' to further tighten the loading sequence.","useSelectively":"Apply fetchpriority=\"high\" only to a single, truly critical image above the fold. Using it on multiple images reduces its effect and may compete with other important resources.","monitorLcp":"After implementation, measure LCP using tools like Lighthouse, PageSpeed Insights or Web Vitals in the browser to confirm that the change improved your LCP timing on real devices.","avoidNonCriticalUse":"Do not use fetchpriority=\"high\" on images that are lazy-loaded, below the fold, or not visually central to the first viewport – this can waste bandwidth and harm overall performance."}},"fontPreload":{"title":"Missing Font Preloading","description":"Critical web fonts used in above-the-fold text are not preloaded. This can cause layout shifts, flash of invisible text (FOIT/FOUT) and slower First Contentful Paint (FCP), all of which negatively affect perceived quality for users and AI performance evaluators.","context":"This task is triggered when fonts used for main UI text or headings (e.g. '<h1>', navigation) are loaded only via @font-face or CSS, but there is no corresponding '<link rel=\"preload\" as=\"font\">' entry in the '<head>'. Without explicit preloading, the browser may delay fetching fonts until later in the render pipeline, causing late text rendering and cumulative layout shift.","recs":{"preloadCriticalFonts":"Add '<link rel=\"preload\" as=\"font\" type=\"font/woff2\" href=\"/path/font.woff2\" crossorigin>' for your primary text and heading fonts that appear above the fold.","includeCrossorigin":"Always include crossorigin=\"anonymous\" (or the appropriate value) on preloaded fonts so the preload can be reused by the @font-face request and not double-download.","limitToKeyFonts":"Preload only the most important fonts (primary regular and bold weights) that are visible on initial view. Avoid preloading every variant to prevent blocking other critical resources.","matchCss":"Ensure that the href in the preload link exactly matches the src URL used in your @font-face declaration (same path, protocol, and query parameters).","testLayoutShift":"After adding preloads, check CLS (Cumulative Layout Shift) and FCP metrics and visually verify that text appears quickly without flicker or late reflows."}},"codeRatio":{"title":"Low Text-to-Code Ratio","description":"Only {ratio}% of your page is actual text content. A very low text-to-code ratio makes it harder for AI crawlers to extract meaningful signals from your HTML, because the relevant content is buried under markup, inline scripts, and styling.","context":"This task is triggered when the ratio of visible text content to total HTML document size drops below a defined threshold. Pages with excessive inline CSS/JS, nested wrappers, or large script blocks but little semantic text provide weak training material for LLMs. AI systems looking for high-quality, information-dense sources may downgrade or ignore pages where content is sparse compared to boilerplate code.","recs":{"reduceInline":"Move large inline '<style>' and '<script>' blocks into external .css and .js files where possible, and minify them. Keep the HTML document focused on semantic structure and content.","removeDeadCode":"Audit your templates for unused components, commented-out HTML, and legacy scripts that can be safely removed to reduce noise.","writeMoreContent":"Increase the amount of high-quality, human-readable text (headings, paragraphs, lists) that explains your topic in depth. Aim for a meaningful body of content, not just a thin landing page.","useSemanticTags":"Wrap content in semantic tags ('<article>', '<section>', '<p>', '<ul>', '<ol>', '<figure>') so AI crawlers can easily separate real content from layout boilerplate.","avoidOverNestedMarkup":"Simplify overly nested '<div>' structures and utility wrappers where possible. Cleaner DOM hierarchies make it easier for both traditional crawlers and LLM-based parsers to understand your page.","monitorTemplateBloat":"If many pages show a low text-to-code ratio, review your CMS or frontend framework patterns (e.g. excessive components, duplicated markup) and refactor to reduce template bloat."}}},"headings":{"h1":{"title":"Incorrect '<h1>' usage","description":"Your page should contain exactly one H1 element that represents the primary topic. Currently found: {count}. Multiple or missing '<h1>' elements send conflicting signals to LLMs and crawlers.","context":"This task is triggered whenever the number of '<h1>' tags is not equal to 1 (0 or >1). It is especially critical on landing pages, product pages, and articles.","recs":{"unique":"Ensure each URL has exactly one '<h1>'. Remove extra '<h1>' tags and use '<h2>'/'<h3>' for subtopics instead.","reflectTopic":"Make the '<h1>' text accurately reflect the main topic in natural language, including key entities or the primary keyword."}},"hierarchy":{"title":"Heading structure skips levels","description":"Heading levels on your page skip steps (e.g. '<h2>' directly followed by '<h4>'), which breaks the semantic document outline. LLMs lose a clear hierarchy of how subtopics relate to main topics.","context":"This task is triggered when the heading sequence jumps by more than one level (e.g. h2 → h4/h5), indicating a structural issue.","recs":{"sequence":"Follow a clean structure: '<h1>' for the main topic, '<h2>' for main sections, '<h3>' for subsections, etc. without jumps.","avoidSkipping":"When introducing new sections, increase heading levels only by one (h2 → h3 → h4). Use CSS for visual styling, not incorrect heading levels."}}},"html":{"p":{"title":"Text not wrapped in '<p>' tags","description":"A significant part of the textual content is not enclosed in '<p>' elements but only in generic containers like '<div>' or '<span>'. LLMs then struggle to detect paragraph boundaries and coherent sense units.","context":"This task is triggered when the ratio between text blocks and '<p>' tags is atypically low (lots of text but very few '<p>' elements).","recs":{"usePTags":"Wrap each real paragraph in a '<p>' element instead of putting text directly into '<div>' or '<span>'.","avoidDivSpan":"Use '<div>'/'<span>' mainly for layout or styling, not for semantic paragraph structure. This helps LLMs analyze text logic more effectively."}},"grouping":{"title":"Missing semantic grouping","description":"Content sections (e.g. features, benefits, testimonials) are not grouped using semantic containers like '<section>' or '<article>'. LLMs see only a flat structure instead of clear topic blocks.","context":"This task is triggered when many headings and content blocks exist but there are no '<section>' or '<article>' elements in the markup.","recs":{"section":"Use '<section>' elements to group related content (e.g. \"Features\", \"Customer Stories\", \"FAQ\"), optionally with aria-labels.","article":"For standalone content like blog posts or news entries, wrap the content in '<article>' so LLMs can treat it as an independent document."}},"nav":{"title":"Missing semantic '<nav>' structure","description":"Navigation exists but is not wrapped in a '<nav>' element. Without '<nav>', crawlers, LLMs, and screen readers cannot clearly distinguish menu areas from regular in-content links.","context":"This task is triggered when typical navigation patterns (logo + main menu, burger menu, footer menu) are detected, but no '<nav>' element is present in the DOM.","recs":{"wrap":"Wrap your main navigation in a '<nav>' element, e.g. '<nav aria-label=\"Main navigation\">'…'</nav>', so crawlers and LLMs can classify it as navigation.","a11y":"If you have multiple menus (header, footer, language switcher), use separate '<nav>' elements with meaningful aria-labels to improve structure and accessibility."}},"lists":{"title":"Unstructured list items","description":"You have '<li>' elements that are not nested inside a '<ul>' or '<ol>'. This violates HTML semantics and makes it harder for LLMs to recognize lists as grouped items.","context":"This task is triggered when '<li>' tags appear in the DOM without an enclosing '<ul>' or '<ol>', often due to CSS-based layout hacks.","recs":{"useUlOl":"Always wrap list items in '<ul>' (unordered) or '<ol>' (ordered) containers.","noLiOutside":"Refactor '<li>' elements outside of lists; use '<div>' or '<p>' if the items are not logically part of a list."}},"tables":{"title":"Table-like data without '<table>'","description":"Tabular structures (rows/columns) were detected but without proper '<table>', '<tr>', '<th>', and '<td>' markup. LLMs cannot reliably interpret the data as a table.","context":"This task is triggered when layout patterns suggest a table built with '<div>' columns/rows but no semantic '<table>' HTML is used.","recs":{"structure":"Use '<table>' as a container and structure rows with '<tr>' and cells with '<th>' (headers) and '<td>' (data).","headerCell":"Mark header cells explicitly with '<th scope=\"col\">' or '<th scope=\"row\">' so LLMs and screen readers can understand relationships between headers and data cells."}},"emphasis":{"title":"Missing semantic emphasis tags","description":"No '<strong>' or '<em>' tags were found. Without these, LLMs cannot see which statements are particularly important or emphasised, especially when emphasis is only applied via CSS.","context":"This task is triggered when there is a lot of body text but no semantic emphasis tags, indicating that emphasis is likely only visual.","recs":{"strongEm":"Use '<strong>' to mark key statements and '<em>' for emphasis or contrast in text. This signals semantic importance to LLMs.","avoidBI":"Avoid using '<b>' and '<i>' purely for styling when semantic emphasis is intended. Prefer '<strong>'/'<em>' and style them via CSS."}}},"images":{"altMissing":{"title":"Missing alt attributes","description":"Detected {count} image(s) without alt attributes. Without alt text, screen readers and LLMs cannot interpret the content of images – they effectively remain invisible to AI search.","context":"This task is triggered when '<img>' elements are found without an alt attribute, except for purely decorative images with role=\"presentation\" or aria-hidden=\"true\".","recs":{"useAlt":"Provide descriptive alt=\"…\" text for all content-bearing images that explains the subject and purpose (e.g. \"Product photo: {productName} front view\").","skipDecorative":"Only leave alt empty (alt=\"\") for purely decorative images and optionally mark them with role=\"presentation\" so LLMs know they can be ignored."}},"altPoor":{"title":"Low-quality alt text","description":"Detected {count} image(s) with generic or unhelpful alt text (e.g. \"image\", \"photo\", \"screenshot\"). Such alt text does not provide any usable information to LLMs.","context":"This task is triggered when alt attributes consist only of generic terms or file names and add no semantic value.","recs":{"describePurpose":"Write alt text that summarizes the information content of the image: what is visible, and what role does the image play in the page context?","avoidVague":"Avoid vague labels like \"image\", \"photo\", or raw file names. Use descriptive language that supports LLMs in understanding context."}},"tagUsage":{"title":"Images should use '<img>' tags","description":"No '<img>' elements were found, but CSS background-image is used. Background images are hard or impossible to interpret for LLMs and many tools.","context":"This task is triggered when background-image is used in CSS but there are no corresponding '<img>' tags in the HTML, especially for meaningful visuals like hero, product, or author images.","recs":{"useImgTag":"Use explicit '<img>' elements with src, alt, and optional width/height for all content-bearing images. Reserve background-image for purely decorative backgrounds.","useBgOnlyDecorative":"If you continue to use CSS backgrounds, ensure that all important information is also available as HTML/text or via a proper '<img>' tag."}},"responsive":{"title":"Missing Responsive Images","description":"Images were detected without a srcset attribute. Without responsive sources, the browser must always download a single fixed image size, which can be unnecessarily large on mobile or too small on high-resolution screens. This hurts performance, Core Web Vitals and, indirectly, how AI systems evaluate page quality.","context":"This task is triggered when '<img>' elements are found that use only src without any srcset/sizes attributes. For AI search and LLMs, performance and UX signals (especially on mobile) increasingly influence which pages are surfaced as high-quality answers. Non-responsive images increase load time, data usage and layout instability, which can negatively affect these quality metrics.","recs":{"addSrcset":"Provide multiple image resolutions via srcset on important images, e.g. '<img src=\"hero-800.jpg\" srcset=\"hero-400.jpg 400w, hero-800.jpg 800w, hero-1600.jpg 1600w\" alt=\"…\">' so the browser can choose the most appropriate asset.","includeSizes":"Always include a sizes attribute that reflects your layout (e.g. sizes=\"(max-width: 768px) 100vw, 50vw\") so the browser can pick the optimal candidate from srcset instead of guessing.","optimizeKeyImages":"Start with above-the-fold and LCP-relevant images (hero, key product visuals). Ensure they have responsive srcset/sizes definitions and are properly compressed (WebP/AVIF where supported).","setDimensions":"Include explicit width and height (or CSS aspect-ratio) for responsive images to prevent layout shift and give the browser enough information to reserve space before the image loads.","avoidOverserving":"Avoid serving a single 2000px-wide image to all devices. Use srcset/sizes to prevent overserving on mobile connections and to improve perceived speed for AI-driven performance scoring."}},"cssBackground":{"title":"Images Hidden in CSS","description":"Important visual content is implemented via CSS background-image instead of '<img>' tags. AI crawlers and accessibility tools primarily parse the DOM, not CSS backgrounds, so these images are effectively invisible for indexing and semantic understanding.","context":"This task is triggered when background-image URLs are detected on elements that appear to contain primary content (e.g. hero sections, key product visuals, explainer graphics) but no corresponding '<img>' tag is present in the markup. For LLMs and search engines, only content exposed in the DOM with proper semantics (img + alt, picture, figure) can be reliably interpreted, associated with entities, and reused in rich results.","recs":{"useImgTag":"Render content-relevant images as standard '<img>' (or '<picture>') elements in the HTML, and reserve CSS background-image primarily for decorative or purely stylistic visuals.","addAltText":"When converting background images to '<img>', add descriptive alt text that explains the purpose of the image (not just \"background\" or \"image\"). This helps both AI systems and assistive technologies.","combineWithFigure":"For key illustrations or diagrams, wrap the '<img>' in a '<figure>' with an optional '<figcaption>' to give AI crawlers additional context about what the image shows.","keepDecorativeInCSS":"Keep truly decorative visuals (patterns, gradients, subtle textures) as CSS backgrounds with role=\"presentation\" or aria-hidden=\"true\" where appropriate, so crawlers focus on meaningful images.","ensureCrawlability":"Avoid using background images for critical content in sliders, hero banners or product galleries. If the image conveys information a user needs, expose it in the DOM as an '<img>' so AI crawlers can \"see\" it."}}},"htmlSemantics":{"semanticGrouping":{"title":"Missing Semantic Structure ('<article>'/'<section>')","description":"No '<article>' or '<section>' tags were found. AI models and search engines rely on these semantic containers to understand which parts of the DOM form the main content, which sections belong together, and how topics are structured across the page. Without them, your page looks like a flat collection of '<div>' blocks with little inherent meaning.","context":"This task is triggered when the page contains substantial text content (multiple headings and paragraphs), but no '<article>' or '<section>' tags are present in the HTML. In modern HTML, '<article>' and '<section>' are key signals for content hierarchy: they tell LLMs which parts are standalone pieces (articles, blog posts, product descriptions) and which are thematic subsections. Without this semantic scaffolding, AI crawlers must guess where one topic ends and another begins, which can dilute topical relevance and snippet extraction quality.","recs":{"wrapInArticle":"Wrap your main content (e.g. a blog post, detailed product description or long-form guide) in a single '<article>' element to signal a self-contained composition, e.g. '<article>…main content…</article>'.","useSectionForChapters":"Use '<section>' tags to group thematically related content blocks inside the article (e.g. '<section>Introduction</section>', '<section>Use Cases</section>', '<section>FAQ</section>'). Each '<section>' should represent a logical chapter or major segment.","pairWithHeadings":"Ensure each '<section>' starts with an appropriate heading ('<h2>' or '<h3>'). This combination of '<section>' + heading gives AI models a strong structural signal for topic hierarchy.","separateAncillaryContent":"Use distinct '<section>' or '<aside>' containers for secondary content such as sidebars, related articles, or CTAs so that AI systems can distinguish main narrative from supporting blocks.","avoidDivOnlyLayouts":"Refactor purely '<div>'-based layouts by replacing structural wrappers with semantic elements ('<header>', '<main>', '<article>', '<section>', '<footer>'). This reduces noise and helps AI parsers interpret the DOM more like a document than an app shell."}},"navTag":{"title":"Missing Semantic Navigation ('<nav>')","description":"Primary navigation links are not wrapped in a '<nav>' element. Without '<nav>', AI crawlers and assistive technologies cannot clearly separate global navigation from the unique page content, making it harder to understand your site architecture and reduce boilerplate noise.","context":"This task is triggered when clusters of internal links (e.g. main menu, footer menu) are detected but not contained within a '<nav>' element. For LLMs and search engines, '<nav>' is a strong signal that a block of links represents navigation rather than body content. This helps them de-emphasise boilerplate menus when analysing page topics and focus on the central content that should rank and be cited.","recs":{"useNavForMenu":"Wrap your primary site-wide menu (usually in the header) in a '<nav>' element, e.g. '<nav class=\"main-nav\">'…menu links…'</nav>'. Do the same for structured footer link groups that act as secondary navigation.","addAriaLabel":"Add an aria-label to distinguish multiple navigation regions, e.g. '<nav aria-label=\"Main menu\">' in the header and '<nav aria-label=\"Footer links\">' in the footer. This helps both screen readers and AI systems interpret their roles.","avoidOverWrapping":"Do not wrap the entire page or unrelated content in '<nav>'. Limit '<nav>' to genuine navigation structures (menus, link lists, breadcrumbs) to keep semantics clean.","structureMenus":"Use '<ul>'/'<li>' inside '<nav>' for menus instead of a flat sequence of '<a>' tags. This creates a predictable, structured pattern that crawlers recognise as navigation.","separateFromContent":"Ensure that main content is placed in '<main>' or '<article>', distinct from '<nav>'. This clear separation makes it easier for AI to ignore navigation noise when extracting topical content."}},"semanticEmphasis":{"title":"Non-Semantic Emphasis Tags","description":"The page uses '<b>' or '<i>' tags for emphasis. These tags are purely visual and do not convey meaning to AI systems. Semantic emphasis tags like '<strong>' and '<em>' signal which words or phrases carry extra importance or change the interpretation of a sentence.","context":"This task is triggered when '<b>' or '<i>' elements are detected in text content while '<strong>' and '<em>' are underused or missing. For LLMs and search engines, semantic emphasis is a valuable hint: '<strong>' indicates importance (e.g. key claims, warnings, core benefits), and '<em>' indicates stress emphasis that can change meaning. Relying only on '<b>'/'<i>' removes this semantic layer, making it harder for AI to identify what truly matters in your copy.","recs":{"useStrong":"Replace '<b>' used for emphasis with '<strong>' when you want to mark key statements (e.g. main benefits, warnings, guarantees). Example: '<strong>30-day money-back guarantee</strong>' instead of '<b>30-day money-back guarantee</b>'.","useEm":"Use '<em>' when you want to stress a word or phrase that changes the nuance or focus of a sentence (e.g. \"We only ship to '<em>verified</em>' business addresses\").","keepBIForStylingOnly":"If you must keep '<b>' or '<i>' for icon fonts or purely stylistic purposes (e.g. italicised brand names), ensure they are not your primary mechanism for emphasising meaningfully important text.","highlightKeyClaims":"Review your most important claims (pricing, guarantees, limitations) and wrap them in '<strong>' so AI systems can better recognise them as central statements of your offer.","avoidOverEmphasis":"Use '<strong>' and '<em>' sparingly and intentionally. Overusing emphasis tags dilutes their semantic value and makes it harder for AI to distinguish truly important content from visual styling."}}},"internalLinking":{"none":{"title":"Missing internal linking","description":"Too few or no internal links were detected. Without internal links, crawlers and LLMs cannot easily understand your information architecture and topic clusters.","context":"This task is triggered when the number of distinct internal paths is below a threshold (e.g. < 5), indicating the page is isolated and poorly connected to the rest of the site.","recs":{"linkRelated":"Add links from this page to related topics, category pages, or pillar content using standard '<a href=\"/path\">' links.","makeCrawlable":"Ensure internal links are crawlable and not hidden behind JavaScript-only interactions or non-standard URL patterns."}},"pillarCluster":{"title":"Missing pillar-cluster linking","description":"There are too few connections between pillar pages and detailed cluster articles. LLMs recognize topical authority much better when this structure is clearly expressed.","context":"This task is triggered when blog/knowledge/category pages have too few links to related detail pages (cluster content) or vice versa.","recs":{"linkToPillar":"Ensure that all cluster articles link back to their pillar (main topic) pages, using descriptive anchor text such as \"Overview: {topic}\".","linkToCluster":"From pillar pages, link out to the most important cluster articles (e.g. \"Further articles on {topic}\") and structure them as lists or a table of contents.","useAnchorText":"Use descriptive anchor text that reflects topic and intent rather than generic labels like \"click here\". This helps LLMs understand the topic graph."}},"descriptiveAnchorText":{"title":"Generic Anchor Text Detected","description":"Found {count} internal link(s) with generic anchor text (e.g. \"click here\", \"read more\"). Generic anchors provide almost no topical signal to AI systems or search engines. Descriptive, keyword-rich anchor text helps models understand what the linked page is about and how it fits into your overall site architecture.","context":"This task is triggered when '<a>' elements are detected whose innerText matches common generic patterns (e.g. \"click here\", \"read more\", \"more\", \"here\") or very short, contextless labels. For LLMs and modern search engines, anchor text is a key relevance signal: it describes the destination URL in natural language and helps AI understand entity relationships, topic clusters and user journeys. Overuse of generic anchors weakens internal linking, makes crawl paths semantically opaque and reduces the chance that linked pages are recognised as strong candidates for specific queries.","recs":{"useDescriptiveText":"Replace generic phrases with descriptive, human-readable anchor text that explains the destination (e.g. \"View AI-SEO pricing\" instead of \"click here\"). Make the anchor text understandable even out of context.","includeKeywords":"Include relevant keywords and entities in the anchor text that reflect the linked page's main topic (e.g. \"AI-SEO audit for e-commerce\" linking to your audit page). This helps AI connect the link target to specific intents and topics.","avoidGenericPhrases":"Avoid anchors like \"click here\", \"read more\", \"more\", \"here\", \"learn more\" without context. If you must use them, at least combine them with descriptive text (e.g. \"Read more about our AI-SEO methodology\").","matchPageIntent":"Align anchor text with the primary intent of the target URL (e.g. use verbs like \"Download\", \"Compare\", \"Calculate\" for tools or downloads, and topic-focused phrases for guides or blog posts). This improves how AI maps links to user tasks.","keepAnchorsConcise":"Keep anchor text concise but specific (typically 2–8 words). Avoid stuffing entire sentences or keyword lists into a single anchor, which can look spammy and reduce clarity for both users and AI.","reviewKeyPaths":"Audit key internal paths (e.g. homepage → product, product → pricing, blog → product) and ensure they use strong descriptive anchor text, as these links carry disproportionate weight for both AI and traditional search."}}},"internationalization":{"langAttr":{"title":"Missing or incorrect '<html lang>' attribute","description":"The '<html>' element does not contain a valid lang attribute (e.g. '<html lang=\"en-US\">'). Without a clean BCP-47 language tag, search engines and LLMs can only guess language and target region heuristically.","context":"This task is triggered when the root element has no lang attribute, uses a placeholder value (e.g. lang=\"en\" on a non-English page), or specifies an invalid code. LLMs combine automatic language detection with the lang attribute; if this signal is missing or wrong, misclassification becomes more likely.","recs":{"setCorrectLang":"Set a valid BCP-47 language tag on the root element, e.g. '<html lang=\"en\">' for generic English, '<html lang=\"en-US\">' for US English, '<html lang=\"de-DE\">' for German (Germany).","alignLangWithContent":"Ensure the lang attribute matches the actual primary content language. Avoid lang=\"en\" on purely German pages, for example.","useRegionCodesIfRelevant":"Use language-region variants (e.g. \"en-GB\", \"fr-CA\") when you explicitly target specific markets and want LLMs to respect those distinctions.","keepLangConsistent":"Keep the lang attribute consistent across all templates and layouts of the same language, so crawlers and LLMs do not receive conflicting signals.","avoidMultipleHtmlTags":"Ensure there is only one '<html>' element with a clearly defined lang attribute and no nested or duplicated HTML roots."}},"hreflang":{"title":"Missing or incomplete hreflang tags","description":"No proper '<link rel=\"alternate\" hreflang=\"…\" href=\"…\">' tags were found for multilingual or country-specific variants. Without hreflang, search engines and LLMs cannot reliably connect language and regional versions of the same content.","context":"This task is triggered when multiple language or locale versions of a page exist (e.g. /en/, /de/, /fr/ or country-specific domains), but there is no consistent hreflang linking between these URLs in the '<head>'. For LLMs, this makes it harder to choose the correct language/region version when generating answers.","recs":{"defineLanguageMatrix":"Create a complete matrix of all language and country variants (e.g. en-US, de-DE, fr-FR) and assign a canonical URL to each variant.","addHreflangLinks":"Add '<link rel=\"alternate\" hreflang=\"xx-YY\" href=\"https://example.com/path\">' tags for each variant in the '<head>'. Each URL should reference all variants including itself.","useXDefault":"Add an x-default entry for a neutral default URL, e.g. '<link rel=\"alternate\" hreflang=\"x-default\" href=\"https://example.com/\">' if you have a global landing page.","keepCodesValid":"Use valid BCP-47 codes (e.g. \"en-GB\", not \"en_GB\" or custom codes). Do not mix language and region codes arbitrarily.","syncWithSitemaps":"Optionally mirror the hreflang structure in XML sitemaps so crawlers and LLMs see language relationships both in HTML and in the sitemap."}}},"structuredData":{"articleProps":{"title":"Incomplete article schema properties","description":"Your Article or BlogPosting schema is missing key properties such as headline, datePublished, or author. LLMs then see less of the publishing context and treat the content more like generic text.","context":"This task is triggered when a @type \"Article\" or \"BlogPosting\" JSON-LD block exists but core fields like headline, datePublished, author, description, or mainEntityOfPage are missing.","recs":{"addHeadline":"Set a descriptive \"headline\" in the Article schema that is consistent with the visible '<h1>' title.","addDate":"Populate \"datePublished\" (and optionally \"dateModified\") with ISO 8601 dates that match visible dates and meta tags.","addAuthor":"Add an \"author\" object with \"@type\": \"Person\" or \"Organization\" and at least a \"name\" and ideally a \"url\" to an author or team page."}},"productProps":{"title":"Incomplete product schema properties","description":"Your Product or Service schema is missing critical fields such as offers or brand. LLMs cannot properly understand price and offer context or compare products.","context":"This task is triggered when a @type \"Product\" or \"Service\" block exists but properties like offers, brand, name, description, image, or sku are missing or empty.","recs":{"addOffers":"Add an \"offers\" property with an Offer object that reflects visible price information (e.g. price, priceCurrency, availability).","addBrand":"Set a \"brand\" property with the brand name as text or as a dedicated Brand/Organization object.","completeProductCore":"Ensure that \"name\", \"description\", \"image\", and ideally an identifier (sku, gtin) are provided so LLMs can uniquely reference the product."}},"orgProps":{"title":"Incomplete organization schema properties","description":"Your Organization schema is missing recommended fields like logo or url. LLMs perceive your brand less clearly as a distinct entity.","context":"This task is triggered when a @type \"Organization\" block exists but core properties like name, url, logo, or sameAs are missing.","recs":{"addLogo":"Add a \"logo\" property with an absolute image URL (HTTPS) that represents your company logo.","addUrl":"Set a \"url\" property with the canonical homepage URL (e.g. \"https://example.com/\").","addSameAs":"Use \"sameAs\" to reference official social and profile pages (LinkedIn, X, GitHub, industry directories) so LLMs can connect your brand across domains."}},"faqProps":{"title":"Incomplete FAQPage schema properties","description":"Your FAQPage schema is missing a proper mainEntity list of Question and Answer objects. LLMs cannot reliably reuse your FAQs as structured Q&A snippets.","context":"This task is triggered when a @type \"FAQPage\" JSON-LD block exists but \"mainEntity\" is missing or contains no valid Question/Answer pairs.","recs":{"addMainEntity":"Build \"mainEntity\" as an array of Question objects, each containing an acceptedAnswer with an Answer object.","mirrorVisibleFAQ":"Ensure that the most important visible FAQ questions are mirrored in schema and that texts match the HTML content."}},"speakable":{"title":"Missing Speakable Schema","description":"No Speakable markup (schema.org SpeakableSpecification) was found on this page. Without it, AI assistants and voice interfaces (e.g. ChatGPT Voice, Google Assistant, Alexa-style systems) have no explicit hint which parts of your content are best suited to be read aloud as concise answers.","context":"This task is triggered when the page is identified as article-like content (e.g. Article, BlogPosting, NewsArticle) but the structured data contains no speakable property referring to a SpeakableSpecification object. For LLMs and voice search experiences, Speakable markup is a strong signal that marks specific sections (selectors) as the canonical, short answer they should read or quote. Without it, AI systems must guess which paragraphs are most suitable for spoken output, which can reduce the quality and consistency of voice answers.","recs":{"addSchema":"Extend your Article/NewsArticle/BlogPosting JSON-LD with a speakable property that points to a SpeakableSpecification object. For example: \"speakable\": { \"@type\": \"SpeakableSpecification\", \"cssSelector\": [\".article-intro\", \"h2#key-facts + p\"] }.","useCssSelector":"Use cssSelector in SpeakableSpecification to reference 1–3 short, well-written sections (intro paragraph, key facts, summary). Avoid marking the entire article as speakable.","keepTextConcise":"Ensure the selected speakable sections are concise and self-contained (typically 20–80 words each), written in clear, natural language suitable to be read aloud without additional context.","alignWithMainAnswer":"Choose speakable sections that directly answer the core question or describe the main topic of the page (e.g. definition, key benefits, short summary). This helps AI voice systems deliver precise answers.","validateSchema":"Validate the extended schema (including SpeakableSpecification) using a structured data testing tool or Schema Markup Validator to ensure the JSON-LD syntax and selectors are valid and parsable.","keepSelectorsStable":"Avoid tying cssSelector values to fragile class names that may change often. Use stable IDs or robust selector patterns so your speakable markup doesn't silently break during redesigns."}},"brokenJson":{"title":"Fix invalid JSON-LD schema","description":"Your page contains JSON-LD structured data that cannot be parsed due to syntax errors (e.g. missing commas, wrong quotes). LLMs and search engines will ignore this markup.","context":"This task is triggered when parsing '<script type=\"application/ld+json\">' blocks throws a JSON error.","recs":{"validate":"Validate your JSON-LD with tools like JSONLint or Google's Rich Results Test and fix all parse errors.","fixSyntax":"Ensure correct JSON syntax: double quotes for keys and strings, commas between properties, no comments or trailing commas."}},"missingTypes":{"title":"Missing relevant schema.org types","description":"For this page type, the expected schema.org @type values (e.g. \"Organization\", \"WebSite\", \"Article\", \"Product\", \"FAQPage\") are missing. Without appropriate types, search engines and LLMs cannot reliably classify the page as a homepage, product detail, knowledge article, FAQ, etc.","context":"This task is triggered when content and layout clearly indicate a specific page type (e.g. product page with price & CTA, article page with title, date & author, FAQ page with many Q&A blocks) but no corresponding schema.org @type exists in any JSON-LD block. For LLMs, these types are strong signals for whether a page should be treated as a product, knowledge source, FAQ, or organization reference.","recs":{"addOrgAndWebsite":"Ensure your domain exposes at least one combined Organization and WebSite schema, e.g. in a global JSON-LD block: { \"@context\": \"https://schema.org\", \"@type\": \"Organization\", ... } and { \"@context\": \"https://schema.org\", \"@type\": \"WebSite\", ... }.","mapTemplatesToTypes":"Define per template which schema.org types must be present: e.g. blog article → \"Article\" or \"BlogPosting\", product detail → \"Product\" or \"Service\", FAQ landing → \"FAQPage\".","useJsonLdInHead":"Implement structured data as JSON-LD in the '<head>' wherever possible. Keep reusable JSON-LD blocks per page type and only inject dynamic fields (name, description, url, image, offers, etc.).","fillKeyProperties":"Whenever you introduce a type (e.g. \"Product\"), always populate key properties: product.name, description, brand, image, offers.price, offers.priceCurrency, offers.availability. For \"Article\", headline, datePublished, author, and description are crucial.","keepTypesConsistent":"Use consistent @type values and property names for the same page type across all URLs so LLMs can learn stable patterns for your site."}},"missingProps":{"title":"Incomplete schema key fields","description":"Some schema.org blocks exist but miss important fields (e.g. name, description, url), so LLMs only see a fragmented representation of your entities.","context":"This task is triggered when structured data is present but core properties are empty, generic (\"Lorem ipsum\", \"Insert Description\"), or completely missing.","recs":{"completeFields":"Ensure all core entities (Organization, WebSite, Article, Product, FAQPage) have at least name, description, and url populated with real values.","avoidPlaceholders":"Remove placeholder texts like \"Insert Description Here\" or \"Dummy\" from schema and replace them with accurate, descriptive content that matches visible text."}},"missingOg":{"title":"Missing Open Graph tags","description":"The following OG tags are missing: {tags}. Without og:title, og:description, og:image, and og:url, many systems (social, chat, LLMs) lack clear preview information for your page.","context":"This task is triggered when the '<head>' is missing core '<meta property=\"og:*\">' tags on pages that are likely to be shared or referenced.","recs":{"addOgTags":"Add at least og:title, og:description, og:image, and og:url to the '<head>' using '<meta property=\"og:title\" content=\"…\" />' etc.","accurateValues":"Ensure OG values match the visible title, meta description, and canonical URL, and choose a compelling og:image (HTTPS, correct format, suitable dimensions)."}},"generalMissing":{"title":"Missing general schema markup","description":"No relevant schema.org types such as Organization, WebSite, Article, Product, or FAQPage were detected on this page. LLMs lack a structured layer for interpreting your content.","context":"This task is triggered when there is HTML content but no JSON-LD or Microdata markup with common schema.org types.","recs":{"addRelevantSchema":"Add appropriate schema.org types for each key page type (e.g. Organization + WebSite on homepage, Article/BlogPosting for blog posts, Product/Service for product pages, FAQPage for FAQ landings).","followGuidelines":"Use JSON-LD as the preferred format and follow schema.org and Google documentation on structured data and rich results."}},"robotsBlocked":{"title":"AI bots blocked by robots.txt","description":"Your robots.txt is blocking access for: {bots}. This prevents important AI crawlers from fully indexing your content. LLMs will then rely more on third-party sources instead of your site directly – you lose control over freshness, context, and brand messaging.","context":"This task is triggered when robots.txt contains Disallow rules for relevant AI and search bots (e.g. OAI-SearchBot, Bingbot, ClaudeBot or similar crawlers), especially for content-heavy sections (e.g. /blog, /products, /docs). For LLMs, this means less direct access to your content, lower AI search visibility, and higher dependency on external, possibly outdated sources.","recs":{"reviewRobots":"Systematically review robots.txt and identify all Disallow rules that affect AI-relevant bots or important content directories. Pay special attention to global rules such as \"User-agent: *\\nDisallow: /\".","defineAIPolicy":"Define a clear AI crawling strategy: which areas should AI bots explicitly be allowed to read (e.g. /blog, /knowledge, /products, /faq) and which areas must remain protected (e.g. /admin, /internal, staging domains)?","whitelistKeyBots":"Explicitly allow key AI and search bots for permitted areas, e.g.: \"User-agent: OAI-SearchBot\\nAllow: /\", \"User-agent: Bingbot\\nAllow: /\" instead of blanket Disallow rules that treat all bots the same.","avoidOverBlocking":"Avoid overly aggressive blocking such as domain-wide Disallow or Disallow for important content directories. Use targeted Disallow rules only for genuinely sensitive paths (e.g. /wp-admin/, /checkout/, /user-data/).","syncWithSitemaps":"Make sure that content relevant to AI search is both allowed in robots.txt and referenced in XML sitemaps so AI crawlers can discover important pages quickly and reliably.","documentDecisions":"Document which bots are allowed and which areas are blocked (and why) so future changes to robots.txt do not accidentally destroy your AI visibility."}}},"metaTags":{"title":{"missing":{"title":"Missing Meta Titles","description":"The following page(s) are missing title tags","context":"This task is triggered when a document lacks a '<title>' element or the element is empty/whitespace. The '<title>' tag is one of the strongest on-page signals for search engines and LLMs to understand what a URL is about. It is also what users see in browser tabs and often in search result snippets. Pages without a proper title are harder to map to queries, topics and entities.","recs":{"addTitle":"Add a unique, descriptive '<title>' element to each HTML document, e.g. '<title>AI-SEO Audit for E-Commerce Shops | GAISEO'.","unique":"Ensure every indexable URL has a unique title that reflects the specific content of that page (not just the brand name). Avoid reusing the same generic title across many pages.","length":"Keep titles roughly between 50–60 characters (including spaces) so they are not truncated in most SERP layouts, while still providing enough context and key terms.","includeBrand":"Append or prepend your brand name where appropriate (e.g. \"… | Brand\"), especially on key landing pages, to support entity recognition by AI systems.","avoidKeywordStuffing":"Do not stuff titles with repeated keywords or separators (e.g. \"AI-SEO, AI-SEO Tool, AI-SEO Software\"). Use natural, readable phrases that clearly describe the page."}},"length":{"title":"Meta Title Length Issues","description":"Some page titles are either too short or too long compared to best-practice ranges. Poorly sized titles can be truncated, rewritten by search engines, or fail to convey enough context to AI models.","context":"This task is triggered when the '' text length falls outside a defined threshold (too short, e.g. < 20 characters, or too long, e.g. > 65–70 characters). Extremely short titles often look generic or unhelpful, while overlong titles are likely to be truncated or rewritten in SERPs and may dilute the main topic signal.","recs":{"optimal":"Adjust titles into an approximate range of 50–60 characters where possible, with a clear primary topic and optionally a brand suffix.","truncation":"Shorten overlong titles so that the most important information (keyword, topic, brand) appears early. Assume that search interfaces may cut off or rewrite text that exceeds their display width.","extendTooShort":"For very short titles, add clarifying context (e.g. instead of \"Pricing\" use \"AI-SEO Platform Pricing & Plans | GAISEO\").","prioritizeKeyTerms":"Front-load the main keyword/entity near the start of the title. Less critical context (brand, site name) can come later.","avoidBoilerplateOverload":"Keep boilerplate (e.g. repeated suffixes) short so it doesn't push unique page information out of the visible area."}},"keyword":{"title":"Meta Titles Missing Target Keywords","description":"The following page title(s) don't contain target keywords: {keywords}. Titles that lack the main terms users search for make it harder for AI systems to confidently associate the page with those intents.","context":"This task is triggered when configured target keywords for a URL or section cannot be matched (case-insensitive, including simple variations) in the '<title>' text. For both search engines and LLMs, the title is a primary place to confirm that a page is relevant to a query or an entity. If the title omits the core topic, the page may be outranked by competitors that explicitly mention it.","recs":{"includeKeyword":"Include at least the primary target keyword (or a very close variant) in the '<title>' tag in a natural, readable phrase.","frontLoad":"Place the primary keyword close to the beginning of the title (e.g. \"AI-SEO Audit for Shopify Stores – …\" instead of \"… – Our Service\"), so it remains visible even when truncated.","useVariants":"Use semantic variants or long-tail forms where appropriate (e.g. \"AI-SEO audit\" vs \"AI-SEO analysis\"), but keep the core concept clearly recognisable.","avoidOverOptimization":"Do not repeat the same keyword multiple times in the title. One strong, well-placed occurrence is usually enough for both users and AI systems.","alignWithContent":"Ensure the keyword(s) used in the title are actually reflected in the on-page content and headings to avoid mismatch signals."}},"duplicate":{"title":"Duplicate Meta Titles","description":"Duplicate titles were found across multiple pages. When many URLs share the same or nearly identical '<title>', AI systems struggle to determine which URL is the best answer for a given query.","context":"This task is triggered when the same '<title>' string appears on multiple distinct URLs (excluding expected duplicates such as pagination where explicitly configured). Duplicate titles make it difficult for search engines and LLMs to understand which page is canonical for a topic and can cause both ranking dilution and suboptimal snippet selection.","recs":{"unique":"Create a unique, descriptive '<title>' for each indexable URL, especially for key landing pages, category pages and articles.","descriptive":"Modify titles to reflect each page's specific content (e.g. include product name, category, location, or audience) instead of using a generic site-wide title.","usePatternsCarefully":"If you use templated titles (e.g. \"{Product} | Brand\"), ensure that the {Product} part is genuinely unique and not repeated across many pages.","deprioritizeNonIndexable":"For pages that should not be indexed (e.g. admin, thin filter pages), use noindex rather than duplicating titles of important pages.","auditKeyClusters":"Pay particular attention to duplicated titles among pages within the same topic cluster (e.g. blog posts in one series). Each should have a distinct angle reflected in the title."}}},"description":{"missing":{"title":"Missing Meta Descriptions","description":"The following page(s) are missing '<meta name=\"description\">' tags. Without them, search engines and AI interfaces must auto-generate snippets, which may be less compelling and not aligned with your messaging.","context":"This task is triggered when no '<meta name=\"description\">' tag is present in the '<head>' or the content attribute is empty. While descriptions are not a direct ranking factor, they strongly influence click-through rates and how AI systems summarise and present your page in answer boxes or cards.","recs":{"add":"Add a clear '<meta name=\"description\" content=\"…\">' tag to each important page that summarises the main value proposition or answer in 1–2 sentences.","compelling":"Write descriptions that encourage clicks: highlight the benefit, include a clear value statement, and match user intent (e.g. \"Compare AI-SEO tools, pricing and features in under 5 minutes.\").","alignWithContent":"Ensure the description accurately reflects on-page content to avoid mismatched expectations that could increase bounce rate.","respectLanguage":"Write descriptions in the same language as the page content so AI models do not treat them as irrelevant noise."}},"length":{"title":"Meta Description Length Issues","description":"Some meta descriptions are either too short or too long compared to best-practice ranges.","context":"This task is triggered when a '<meta name=\"description\">' content value is shorter than a configured minimum (e.g. < 70–80 characters) or longer than a typical upper bound (e.g. > 170–180 characters). Very short descriptions often fail to convey enough context; overly long ones risk being truncated or ignored in favour of auto-generated text.","recs":{"optimal":"Aim for roughly 150–160 characters for most descriptions. This usually fits well into common snippet widths while still allowing a meaningful summary.","truncation":"For very long descriptions, move the most important information (intent, benefit, key entity) near the beginning so it remains visible even if truncated.","enrichTooShort":"Extend overly short descriptions with a clear explanation of what the page offers (who it is for, what problem it solves, what users can do/learn).","avoidKeywordLists":"Do not treat the description as a keyword list. Instead, write natural sentences that LLMs can reuse as concise summaries."}},"keyword":{"title":"Meta Descriptions Missing Keywords","description":"The following meta description(s) do not contain target keywords: {keywords}. Without mentioning the main terms, descriptions are less likely to be reused as relevant snippets for those queries.","context":"This task is triggered when target keywords for the page cannot be matched in the '<meta name=\"description\">' content. While search engines may sometimes ignore the description, including key terms in a natural way increases the chance that the snippet seems aligned with the query and is reused by AI systems in search results or conversational answers.","recs":{"include":"Include one or two relevant target keywords (or close variants) in the description so that both users and AI systems can immediately see the topic relevance.","natural":"Use keywords in natural, readable sentences instead of forced insertions. AI models prefer coherent text they can quote directly.","supportLongTail":"Where appropriate, reflect long-tail intent in the description (e.g. \"… for B2B SaaS marketing teams\"), not just the head term.","avoidStuffing":"Avoid repeating the same keyword multiple times in the description. One or two well-placed mentions are enough."}}},"openGraph":{"missing":{"title":"Missing Open Graph Tags","description":"Missing Open Graph tags: {missing}. Without these, you lose control over how your content appears when shared on platforms like Facebook, LinkedIn or messaging apps, and AI systems get weaker social context signals.","context":"This task is triggered when core Open Graph meta tags (e.g. og:title, og:description, og:image, og:url) are missing from the '<head>'. These tags define how URLs are rendered in link previews on social networks and some chat interfaces. Strong, consistent OG metadata also helps AI systems understand which image and which text best represent the page.","recs":{"addTags":"Add at minimum og:title, og:description, og:image and og:url to the '<head>' for shareable pages. Example: '<meta property=\"og:title\" content=\"AI-SEO Audit for E-Commerce\" />'.","socialSharing":"Align og:title and og:description with your main value proposition. Use slightly more emotional or benefit-driven copy than the plain HTML title if appropriate.","imageSize":"Use a high-quality og:image with at least 1200x630px (1.91:1 aspect ratio) in a widely supported format (JPEG/PNG/WebP). Ensure the image is accessible via an absolute URL.","consistentUrl":"Set og:url to the canonical, preferred URL of the page. This helps consolidate share metrics and prevents split signals for duplicates.","testPreviews":"Test how your pages render on major networks (LinkedIn, Facebook, Slack, etc.) to ensure OG tags are being picked up correctly."}}},"twitter":{"missing":{"title":"Missing Twitter Card Tags","description":"Missing core Twitter Card tags: {missing}. Without them, X/Twitter has to guess how to render your link, which can lead to poor or inconsistent previews.","context":"This task is triggered when no Twitter Card meta tags (e.g. twitter:card, twitter:title, twitter:description, twitter:image) are present in the '<head>'. These tags tailor how your content appears on X/Twitter and in some third-party clients that respect Twitter's card protocol.","recs":{"addTags":"Add the essential Twitter Card tags, e.g. '<meta name=\"twitter:card\" content=\"summary_large_image\">', twitter:title, twitter:description, twitter:image.","cardType":"Use twitter:card=\"summary_large_image\" for most landing pages and articles to achieve a large, visually engaging preview.","validate":"Validate your implementation using a Twitter Card preview/validator to confirm that tags are read correctly and images are not blocked.","reuseOg":"You can reuse og:title/og:description values for twitter:title/twitter:description to keep messaging consistent and reduce maintenance effort."}},"missingImage":{"title":"Twitter Card Image Recommended","description":"twitter:image is missing or not set. Adding a dedicated image improves how your content appears when shared on X/Twitter, increasing visibility and click-through rates.","context":"This task is triggered when a Twitter Card is present but no twitter:image tag is defined. Without a card image, your link may show as text-only or with an automatically chosen image that does not reflect your brand or content.","recs":{"addImage":"Add '<meta name=\"twitter:image\" content=\"https://…/image.jpg\">' with a compelling, on-brand image that clearly represents the page.","imageSize":"Use an image that matches the recommended aspect ratio for summary_large_image (around 1.91:1, e.g. 1200x628 or 800x418) so it renders correctly without cropping.","alignWithOgImage":"Where possible, align twitter:image with og:image to keep previews consistent across platforms, unless you have a Twitter-specific creative.","useAbsoluteUrl":"Always use an absolute, HTTPS URL for twitter:image so that clients can fetch it reliably."}}}},"canonical":{"missing":{"title":"Missing Canonical Tag","description":"Page {url} is missing a '<link rel=\"canonical\">' tag. Without a canonical URL, search engines and AI systems must guess which version of similar content is the primary one.","context":"This task is triggered when an indexable HTML page has no '<link rel=\"canonical\" href=\"…\">' element in the '<head>'. Canonical tags are crucial for indicating the preferred URL among duplicates (e.g. tracking parameters, filters, HTTP vs. HTTPS). Without them, link equity and relevance signals can be split across multiple URLs, and AI systems may pick suboptimal variants for citation.","recs":{"addCanonical":"Add a '<link rel=\"canonical\" href=\"https://example.com/path/\">' tag to every indexable page to declare the preferred URL.","selfReferencing":"For unique, non-duplicate pages, use a self-referencing canonical (canonical href equals the clean, final URL of the page).","absolute":"Always use absolute URLs (including protocol and domain) in canonical tags to avoid ambiguity across subdomains or schemes.","avoidMultiple":"Ensure only one canonical tag is present per page. Multiple conflicting canonical tags can cause search engines to ignore them."}},"relative":{"title":"Canonical Tag Uses Relative URL","description":"Page {url} defines a canonical link with a relative URL: {canonical}. Relative canonicals can be interpreted inconsistently across crawlers and may lead to unexpected canonicalisation.","context":"This task is triggered when the canonical '<link>' uses a relative href (e.g. \"/page\" instead of \"https://example.com/page\"). Some crawlers and tools may resolve this correctly, but best practice is to use full, absolute URLs for clarity and consistency.","recs":{"useAbsolute":"Update the canonical to use an absolute URL, e.g. '<link rel=\"canonical\" href=\"https://example.com{canonical}\">'.","includeProtocol":"Always include the protocol (https://) and full domain in the canonical href so there is no doubt about the canonical host and scheme.","keepDomainConsistent":"Ensure the domain in canonical URLs matches your primary domain (avoid mixing www and non-www unless intentionally configured)."}},"different":{"title":"Canonical Points to Different Page","description":"Page {url} has a canonical that points to a different URL: {canonical}. This tells search engines that {canonical} is the preferred version, which may be correct (for duplicates) or a misconfiguration.","context":"This task is triggered when the canonical href on a page does not match the page URL itself. This can be intentional (e.g. parameterised URL canonicalising to a clean version) or accidental (e.g. copy-pasted canonical from a template). Misconfigured cross-canonicals can cause important pages to be effectively de-indexed.","recs":{"verify":"Review whether {url} is genuinely a duplicate or variant of {canonical}. If not, the canonical is likely wrong and should be changed.","selfReferencing":"For unique, stand-alone pages that should rank independently, set the canonical to the page's own clean URL.","useForVariantsOnly":"Use cross-page canonicals for true duplicates or near-duplicates (e.g. tracking parameters, sort orders), not for distinct content like different products or articles.","checkTemplates":"Audit your templates and CMS logic to ensure canonical URLs are generated dynamically per page and not hard-coded from another URL."}},"http":{"title":"Canonical Uses HTTP Instead of HTTPS","description":"The canonical tag for this page uses HTTP instead of HTTPS: {canonical}. This conflicts with modern best practices and may split signals between HTTP and HTTPS versions.","context":"This task is triggered when the canonical href contains an http:// URL on a site that is expected to use HTTPS as the primary protocol. Mixing HTTP and HTTPS in canonicals can confuse crawlers and cause ranking signals to be distributed across multiple protocol versions.","recs":{"useHttps":"Update the canonical URL to use https://, matching your site's primary protocol and redirect rules.","consistency":"Ensure all canonical tags across the site consistently use HTTPS so that search engines consolidate all signals on the secure version.","checkRedirects":"Verify that the HTTP version of {canonical} redirects to its HTTPS counterpart and adjust any legacy template values accordingly."}},"invalid":{"title":"Invalid Canonical URL","description":"Page {url} has an invalid canonical value: {canonical}. This may be a malformed URL (missing scheme/host) or contain characters that make it unusable for crawlers.","context":"This task is triggered when the canonical href does not conform to a valid URL format (e.g. missing protocol, contains spaces, JavaScript URIs, or relative patterns that cannot be resolved). Invalid canonical tags are typically ignored by search engines, leaving the page without a reliable canonical signal.","recs":{"fixUrl":"Update the canonical href to a syntactically valid absolute URL (e.g. \"https://example.com/page\"). Avoid JavaScript pseudo-URLs or relative fragments.","validFormat":"Use a standard URL format: protocol (https://), domain, optional path and query string, without spaces or invalid characters.","avoidDynamicPlaceholders":"Ensure your CMS or templates do not output placeholder values (e.g. \"{{canonical}}\") when configuration is missing.","revalidate":"After fixing the canonical, test the page in search/SEO tools to confirm that the new canonical is being detected and respected."}}},"robots":{"missing":{"title":"Missing robots.txt File","description":"Your website doesn't have a robots.txt file. This makes it harder for search engines to crawl your site efficiently.","context":"This task is triggered when no robots.txt file is found at the root of your domain. Search engines and AI crawlers use robots.txt to understand crawling permissions and discover sitemaps.","recommendation1":"Create a robots.txt file in your website's root directory","recommendation2":"Include sitemap reference and proper crawling directives"},"searchEngineBlocked":{"title":"Search Engines Blocked by robots.txt","description":"Your robots.txt file is blocking important search engine crawlers: {bots}. This prevents your site from appearing in search results.","context":"This task is triggered when robots.txt contains Disallow rules for Googlebot or Bingbot on important content paths. Blocking these crawlers prevents your pages from being indexed in search results.","recommendation1":"Review and update your robots.txt file to allow search engine crawlers","recommendation2":"Ensure Googlebot and Bingbot can access your important pages"},"aiCrawlerBlocked":{"title":"AI Crawlers Blocked by robots.txt","description":"Your website is blocking AI crawlers ({bots}) from accessing your content. This may reduce your site's discoverability in AI-powered search and assistants.","context":"This task is triggered when robots.txt blocks AI-related crawlers like GPTBot, Google-Extended, ClaudeBot, or CCBot. Blocking these reduces your visibility in AI-powered search results and chatbot responses.","recommendation1":"Consider allowing AI crawlers to improve content discoverability","recommendation2":"Review your robots.txt file and adjust AI crawler permissions"},"missingSitemap":{"title":"No Sitemap Reference in robots.txt","description":"Your robots.txt file doesn't include a sitemap reference. Adding this helps search engines discover and index your pages more efficiently.","context":"This task is triggered when robots.txt exists but contains no Sitemap: directive. Including a sitemap reference helps crawlers discover all your important pages quickly.","recommendation1":"Add a Sitemap: directive to your robots.txt file","recommendation2":"Ensure your sitemap is up-to-date and accessible"}},"https":{"noHttps":{"title":"HTTPS Not Available","description":"Your website does not support HTTPS. This is a critical security issue that affects user trust and search engine rankings.","recommendation1":"Obtain an SSL/TLS certificate from a trusted certificate authority","recommendation2":"Install the certificate on your web server","recommendation3":"Configure your server to serve content over HTTPS"},"noHttpsRedirect":{"title":"HTTP Not Redirecting to HTTPS","description":"Some HTTP URLs ({urls}) are accessible without redirecting to HTTPS. This creates security risks and duplicate content issues.","recommendation1":"Configure server-side redirects from HTTP to HTTPS (301 permanent redirects)","recommendation2":"Update your .htaccess or server configuration to force HTTPS","recommendation3":"Enable HSTS (HTTP Strict Transport Security) headers"},"inconsistentCanonical":{"title":"Inconsistent Canonical URLs","description":"Your website resolves to {count} different URLs: {urls}. This causes duplicate content issues and dilutes AI-SEO value.","recommendation1":"Choose one canonical version (preferably HTTPS with or without www)","recommendation2":"Set up 301 redirects from all variants to your chosen canonical URL","recommendation3":"Update your canonical tags to point to the same version"},"canonicalMismatch":{"title":"Canonical Tag Mismatch","description":"Your canonical tag points to {canonical} but the actual URL resolves to {actual}. This confuses search engines.","recommendation1":"Update your canonical tag to match the final URL after redirects","recommendation2":"Ensure consistency between redirects and canonical tags"}}}},"DashboardPage":{"dashboard":"Dashboard","dbSchema":"DB Schema","websiteCheck":"Website Check","optimization":"Optimization","profile":"Profile","audit":"Audit","noData":"No data available","globalSearch":"Global Search...","administrator":"Administrator","pageTitle":"Your dashboard","settings":"Settings","notifications":"Notifications","helpAndSupport":"Help & Support","logout":"Logout","filters":"Filters","timeRange":"Time Range","lastWeek":"Last Week","lastQuarter":"Last Quarter","lastYear":"Last Year","tool":"Tool","allTools":"All Tools","country":"Country","germany":"Germany","usa":"USA","unitedKingdom":"United Kingdom","france":"France","visibilityScore":"Visibility Score","visibilityScoreTooltip":"Estimated visibility of your brand, domain, or content in AI-powered search engines such as ChatGPT, Perplexity, and Gemini. The score approximates how often you are mentioned, recommended, or cited in AI-generated answers that reflect your target customers' personas, intents, questions, and core topics.","current":"Current","lastMonthShort":"Last Month","average":"Average","competitiveAnalysis":"Competitive Analysis","competitiveAnalysisTooltip":"Estimated comparison of your AI visibility versus key competitors, based on typical customer intents and behaviors. The score reflects how likely AI systems are to reference your brand compared to others for the same topics, questions, and use cases. Your domain is shown alongside competitor domains to highlight relative positioning and authority.","competitors":"Competitors","others":"Others","yourBrand":"Your Brand","sentimentAnalysis":"Sentiment Analysis","sentimentAnalysisTooltip":"Indicates how AI systems talk about your brand in terms of tone and perception. It analyzes whether mentions are positive, neutral, or negative across AI-generated answers. A strong sentiment score means your brand is associated with trust, credibility, and positive context in AI search.","positive":"Positive","neutral":"Neutral","negative":"Negative","optimizationScore":"Optimization Score","optimizationScoreTooltip":"Evaluates how well your website is structured and optimized for AI search. This includes content clarity, semantic structure, technical signals, freshness, and AI-readable elements. The score summarizes how effectively your site supports AI understanding, citation, and recommendation.","optimal":"Optimal","category":"Category","status":"Status","progress":"Progress","criticalStatus":"Critical","optimalStatus":"Optimal","improvableStatus":"Improvable","tasks":"Tasks","showAll":"Show All","open":"Open","completed":"Completed","all":"All","showMore":"Show more","metaDataHeadings":"Meta Data & Headings","productPagesContent":"Product Pages Content & Markup","loadTimeWebVitals":"Load Time & Core Web Vitals","aiOptimization":"AI Optimization & Actuality","indexabilityRobots":"Indexability & Robots Control","structuredData":"Structured Data","high":"high","medium":"medium","low":"low","critical":"critical","createDailyBriefing":"Create daily briefing","addMissingTitles":"Add missing page title markups","updateContent":"Update content","removeOldContent":"Remove outdated content","implementSchemaMarkup":"Implement schema markup","optimizeWebVitals":"Optimize Core Web Vitals","performCompetitorAnalysis":"Perform competitor analysis","reviseMetaDescriptions":"Revise meta descriptions","selectCountry":"Select country","lastMonth":"Last Month","last3Months":"Last 3 Months","last6Months":"Last 6 Months","custom":"Custom","latest":"Latest","subscription":"Subscription","loadingReport":"Loading your AI-SEO report...","errorLoadingReport":"There has been an error loading the reports.","gemini-2-5-pro":"Gemini","sonar-pro":"Perplexity","ChatGPT":"OpenAI","loading":"Generating your AI-SEO report...","seoGenerating":"AI-SEO results are being generated. This could take a few minutes...","loadingData":"Refreshing data...","errorLoading":"We couldn't generate your AI-SEO report.","brandSetupPendingTitle":"Brand Setup Pending","brandSetupPendingMessage":"Your subscription is active, but your brand is still being created. This usually takes just a few moments.","noReportsTitle":"Your Report is Being Generated","noReportsMessage":"Your AI-SEO report is currently being generated. This process typically takes a few minutes. You'll receive an email notification once it's ready. If you don't see the email, please check your spam folder and mark it as 'not spam' to ensure future notifications arrive in your inbox.","refreshButton":"Refresh Page","selectDates":"Select dates","apply":"Apply","cancel":"Cancel","statusLabel":{"optimal":"Optimal","optimizable":"Optimizable","critical":"Critical"},"param":{"structuredData":"Structured Data","internationalization":"Internationalization","internalLinking":"Internal Linking","images":"Images","headings":"Headings","freshness":"Freshness","faq":"FAQ","eta":"Expertise, Authority, Trust","contentQuality":"Content Quality & Relevance","htmlSemantics":"HTML Semantic Structure","headerFooter":"Header & Footer","technicalAiSeo":"Technical AI-SEO"}},"LoginPage":{"signIn":"Sign in","subtitle":"Enter your credentials","email":"Email","emailPlaceholder":"m@example.com","password":"Password","forgot":"Forgot your password?","orContinue":"Or continue with","signInWithGoogle":"Continue with Google","noAccount":"Don't have an account?","createAccount":"Create an Account","unexpectedError":"An unexpected error occurred. Please try again.","invalidCredentials":"Invalid email or password. If you haven't verified your email yet, please check your inbox.","googleFailed":"Google sign‑in failed. Please try again.","hidePassword":"Hide password","showPassword":"Show password","passwordMust":"Password must:","passwordMin":"be at least 8 characters long","passwordLetter":"contain at least one letter","passwordNumber":"contain at least one number","passwordSpecial":"contain at least one special character","emailInvalid":"Please enter a valid email address","emailNotVerified":"Your email is not verified. Please check your inbox for the verification email.","verificationEmailResent":"Verification email sent! Please check your inbox.","didntReceiveEmail":"Didn't receive email? Resend","resending":"Resending...","pageTitle":"Sign in"},"SignUpPage":{"createAccount":"Create an Account","subtitle":"Enter your information to get started","name":"Name","email":"Email","password":"Password","confirmPassword":"Confirm Password","signupError":"An error occurred during sign up. Please try again.","signupSuccess":"Account created successfully! Please check your email to verify your account before signing in.","alreadyHaveAccount":"Already have an account?","nameMin":"Name must be at least 2 characters","nameMax":"Name must be less than 50 characters","emailInvalidSignUp":"Please enter a valid email address","passwordMinSignUp":"Password must be at least 8 characters long","passwordLetterSignUp":"Password must contain at least one letter","passwordNumberSignUp":"Password must contain at least one number","passwordSpecialSignUp":"Password must contain at least one special character","confirmMatch":"Passwords do not match","showPassword":"Show password","hidePassword":"Hide password","signIn":"Sign in","passwordMust":"Password must:","verifyEmailMessage":"Please check your email to verify your account.","verificationEmailResent":"Verification email sent! Please check your inbox.","didntReceiveEmail":"Didn't receive email? Resend","resending":"Resending...","emailAlreadyExists":"User with this email already exists.","userCreationFailed":"Failed to create user. Please try again.","unknownError":"An unknown error occurred. Please try again.","pageTitle":"Create your account"},"LayoutMeta":{"title":"GAISEO – AI-SEO & Website Optimization","description":"GAISEO makes your website AI-ready: visibility scores, competitor insights, and code-level optimization in one solution.","ogTitle":"GAISEO – your code based AI-SEO Analysis"},"userSettings":{"title":"Settings","description":"Description","checkInputs":"Please check your inputs","saveFailed":"Failed to save settings","websiteConfiguration":"Website Configuration","configureWebsiteSubdomains":"Configure your main website and subdomains for analysis","mainWebsiteUrl":"Main Website URL","enterMainDomain":"Enter your main domain without http:// or https://","subdomains":"Subdomains","addSubdomainsAnalysis":"Add subdomains you want to include in the analysis","addSubdomain":"Add subdomain","businessInformation":"Business Information","businessDetailsContext":"Provide details about your business for better analysis context","brandName":"Brand Name","yourBrandName":"Your Brand Name","industry":"Industry","selectIndustry":"Select industry","productServiceDescription":"Product/Service Description","describeMainProduct":"Describe your main product or service","briefDescription":"Brief description of what you offer","geographicTargeting":"Geographic Targeting","selectCountriesSEO":"Select the countries where you want to focus your AI-SEO analysis","targetCountries":"Target Countries","addCountry":"Add a country","settingsPreview":"Settings Preview","currentConfiguration":"Current configuration that will be saved","unsavedChanges":"You have unsaved changes","resetToDefault":"Reset to Default","saveSettings":"Save Settings","saving":"Saving...","saveSuccess":"Settings saved successfully!","selectCountries":"Select Countries","selectCountriesPlaceholder":"Select countries...","countrySelected":"country selected","countriesSelected":"countries selected","countriesSelectedCount":"countries selected","searchCountries":"Search countries...","noCountryFound":"No country found.","editCountries":"Edit Countries","selectTargetCountries":"Select Target Countries","selectCountriesDescription":"You can pick up to 3 countries.","cancel":"Cancel","confirmSelection":"Confirm Selection","selectedCountries":"Selected Countries","selected":"selected","previewTitle":"Your Settings (Preview Only)","previewDescription":"This is a read-only preview. Contact support to update your settings.","supportSection":"Need Help?","supportMessage":"If you need to update your settings or have any questions, our support team is here to help.","supportContact":"Contact Support","supportEmail":"contact@gaiseo.com","supportEmailSubject":"Settings Update Request - GAISEO Account","none":"None","back":"Back to Dashboard","failedToLoad":"Failed to load settings.","confirmSaveTitle":"Are you sure you want to save?","confirmSaveDescription":"Once saved, you won't be able to edit your settings without contacting an admin.","confirm":"Yes, Save","pages":"Pages","addPagesAnalysis":"Add specific pages you want to include in the analysis (e.g. /about-us, /contact).","pageRequired":"Page path is required","pageExists":"This page is already added","pageInvalid":"Invalid page format. Use relative paths like /about-us","configureWebsitePages":"Configure your main website and specific pages for analysis.","websiteUrl":"Website URL","mainWebsiteAddress":"Your main website address","mainUrl":"Main URL","urlPlaceholder":"https://example.com","subdomainsOptionalMax3":"Additional subdomains to analyze (optional, max 3)","subdomainPlaceholder":"e.g., blog.example.com or shop.example.com","addSubdomainButton":"Add Subdomain","specificPagesOptional":"Specific Pages (Optional)","specificPagesDescription":"Specific URLs for detailed analysis (max 10)","pageUrls":"Page URLs","pagePlaceholder":"e.g., about, pricing, /contact, /blog/post","addPageButton":"Add Page","brandInformation":"Brand Information","tellUsAboutBusiness":"Tell us about your business","product":"Product","productPlaceholder":"e.g., Marketing Analytics Software","industryLabel":"Industry","industryPlaceholder":"e.g., SaaS, E-commerce, Healthcare","brand":"Brand","brandPlaceholder":"e.g., Acme Corp","descriptionPlaceholder":"Brief description of your product or service...","customerPersonas":"Customer Personas","customerPersonasDescription":"Define your target customer profiles (1-5 personas)","personas":"Personas","persona":"Persona","removePersona":"Remove Persona","personaName":"Name","personaNamePlaceholder":"e.g., Marketing Manager","age":"Age","agePlaceholder":"e.g., 30-45","traits":"Traits","traitsPlaceholder":"e.g., Tech-savvy, data-driven","needs":"Needs","needsPlaceholder":"e.g., Better analytics, time savings","painPoints":"Pain Points","painPointsPlaceholder":"e.g., Complex tools, high costs","addPersonaButton":"Add Persona","countries":"Countries","countriesDescription":"Target countries for AI-SEO analysis (1-3 countries)","selectCountry":"Select a country","submitButton":"Submit Settings","submitting":"Submitting...","logout":"Logout"},"profile":{"title":"Profile","description":"Manage your account information and preferences","personalInformation":"Personal Information","personalInfoDescription":"Your account details and personal information","accountInformation":"Account Information","accountInfoDescription":"Account details and authentication information","name":"Full Name","email":"Email Address","provider":"Sign-in Method","providerCredentials":"Email & Password","providerGoogle":"Google Account","profilePicture":"Profile Picture","accountId":"Account ID","lastSignIn":"Last Sign In","signInMethod":"Sign-in Method","changePassword":"Change Password","updateProfile":"Update Profile","deleteAccount":"Delete Account","confirmDelete":"Are you sure you want to delete your account?","dangerZone":"Danger Zone","dangerZoneDescription":"Irreversible actions that affect your account","supportSection":"Need Help?","supportMessage":"If you need to update your profile or have any questions, our support team is here to help.","supportContact":"Contact Support","supportEmail":"help@gaiseo.com","supportEmailSubject":"Profile Support Request - GAISEO Account","back":"Back to Dashboard","backToDashboard":"Back to Dashboard","noProfilePicture":"No profile picture"},"brandSettings":{"title":"Settings","description":"View your configured brand information","noBrandConfigured":"No brand configured yet. Please configure your brand settings.","brandInformation":"Brand Information","brandInformationDescription":"Core information about your brand","brandName":"Brand Name","productService":"Product/Service","industry":"Industry","websiteUrl":"Website URL","brandDescription":"Description","targetMarkets":"Target Markets","targetMarketsDescription":"Countries where you operate","subdomains":"Subdomains","subdomainsDescription":"Additional subdomains analyzed","developmentPages":"Development Pages","developmentPagesDescription":"Specific pages analyzed","customerPersonas":"Customer Personas","customerPersonasDescription":"Target audience profiles","personaNameAge":"Name & Age","personaTraits":"Traits","personaNeeds":"Needs","personaPainPoints":"Pain Points","backToDashboard":"Back to Dashboard"},"industries":{"technology":"Technology","healthcare":"Healthcare","finance":"Finance","ecommerce":"E-commerce","education":"Education","realEstate":"Real Estate","travel":"Travel","foodBeverage":"Food & Beverage","fashion":"Fashion","automotive":"Automotive","entertainment":"Entertainment","other":"Other"},"validation":{"urlRequired":"Website URL is required","urlInvalid":"Please enter a valid domain (e.g., example.com)","brandRequired":"Brand name is required","industryRequired":"Please select an industry","productRequired":"Product description is required","countryRequired":"At least one country must be selected","pageInvalid":"Invalid page path format","pageEmpty":"Please enter a page path","pageExists":"This page has already been added","productTooLong":"Product description must be less than 200 characters","brandTooLong":"Brand name must be less than 100 characters","tooManyCountries":"Maximum 10 countries allowed","maxPagesReached":"Maximum 4 pages allowed","personaNameRequired":"Persona name is required","personaNameTooLong":"Name must be 100 characters or less","personaAgeRequired":"Age range is required","personaAgeTooLong":"Age range must be 50 characters or less","personaTraitsRequired":"Traits are required","personaTraitsTooLong":"Traits must be 500 characters or less","personaNeedsRequired":"Needs are required","personaNeedsTooLong":"Needs must be 500 characters or less","personaPainPointsRequired":"Pain points are required","personaPainPointsTooLong":"Pain points must be 500 characters or less","urlCannotContainSpaces":"URL cannot contain spaces","urlMustBeValid":"Must be a valid URL (e.g., example.com or https://example.com)","subdomainCannotBeEmpty":"Subdomain cannot be empty","subdomainTooLong":"Subdomain must be 100 characters or less","pagePathCannotBeEmpty":"Page path cannot be empty","pagePathTooLong":"Page path must be 200 characters or less","maxSubdomainsAllowed":"Maximum 3 subdomains allowed","maxPagesAllowed":"Maximum 10 pages allowed","productNameRequired":"Product name is required","productNameTooLong":"Product name must be 200 characters or less","industryTooLong":"Industry must be 200 characters or less","brandNameTooLong":"Brand name must be 200 characters or less","descriptionTooShort":"Description must be at least 10 characters","descriptionTooLong":"Description must be 1000 characters or less","atLeastOnePersonaRequired":"At least one customer persona is required","maxPersonasAllowed":"Maximum 5 customer personas allowed","subdomainMustBelongToDomain":"Subdomain must belong to {domain}","pageMustBelongToDomain":"Page must belong to {domain}","countryCodeMustBeTwoChars":"Country code must be exactly 2 characters","countryCodeMustBeUppercase":"Country code must be 2 uppercase letters","maxCountriesAllowed":"Maximum 3 countries allowed"},"subscribe":{"title":"Choose Your Plan","description":"Unlock the full power of GAISEO with a plan that fits your needs.","toggle":{"monthly":"Monthly","yearly":"Yearly"},"plugin":{"name":"GAISEO Plugin","subtitle":"WordPress plugin","description":"The GAISEO Plugin brings AI-SEO directly into WordPress. With 30+ checks and an AI toolbox including alt-text generation, FAQ creation, an HTML header creator, and automatic time tag updates, you can make your content AI-ready hands-on.","features":["30+ AI-SEO checks in 10 categories","AI-generated alt-texts & FAQs (multilingual)","HTML header creator","Auto time tag updates","Batch processing & WP integration"],"price":"Join Waitlist","buttonText":"Join Waitlist","buttonLink":"https://gaiseo.com/join-waitlist/"},"pro":{"name":"GAISEO Pro","subtitle":"SaaS Solution","description":"GAISEO Pro gives you real-time insights into your AI search visibility – with clear scores for Visibility, Sentiment, and Competitors. The dashboard analyzes up to 5 pages or subpages per month across 11 parameters, focusing on HTML structure and semantic clarity. You'll get a prioritized to-do list with code snippets for instant improvements.","features":["Real-time scores: Visibility, Sentiment & Competitors","5 pages/subpages analysis (11 parameters)","Detailed HTML structure check","43+ actionable tasks with code snippets","Dashboard with visualizations & updates"],"price":"€99","yearlyPrice":"€79","yearlyNote":"(= €948 / year instead of €1,188)","isPopular":true},"enterprise":{"name":"GAISEO Enterprise","description":"GAISEO Enterprise is built for companies scaling AI-SEO. In addition to all Pro features, you get flexible scans for domains and subpages, personal consulting, and tailored reports for your team. A dedicated account manager supports you with analysis, optimization, and implementation – including extended visibility analysis.","features":["All Pro features, no limits","Consulting & workshops","Extended management reports","Dedicated support & roadmap"],"price":"Talk to Sales","buttonText":"Talk to Sales","buttonLink":"https://calendly.com/cosima-gaiseo/30min"},"selectButton":"Select","joinNow":"Join Now","topSeller":"TOP SELLER","perMonth":"/month","earlyAccess":"Early Access"},"PaymentSuccessPage":{"processing":"Processing your payment...","errorTitle":"Payment Error","errorMessage":"We couldn't verify your payment. Please contact support if this is unexpected.","successTitle":"Payment Successful","thankYou":"Thank you, {name}!","charged":"You've been charged {amount} {currency}.","goDashboard":"Go to Dashboard","backHome":"Back to Home"},"VerifyEmailPage":{"title":"Verify Your Email","verifying":"Verifying your email...","success":"Email verified successfully!","failed":"Verification failed","verifyingMessage":"Please wait while we verify your email address...","successMessage":"Your email has been verified successfully. You can now sign in to your account.","errorMessage":"We couldn't verify your email. The link may have expired or is invalid.","missingToken":"No verification token provided. Please check your email for the correct link.","verificationFailed":"Email verification failed. Please try again or request a new verification email.","unexpectedError":"An unexpected error occurred. Please try again.","goToLogin":"Go to Sign In","backToSignup":"Back to Sign Up"},"ForgotPasswordPage":{"title":"Forgot Password","subtitle":"Enter your email address and we'll send you a reset link","email":"Email","emailPlaceholder":"m@example.com","sending":"Sending...","sendResetLink":"Send Reset Link","backToLogin":"Back to Sign In","successMessage":"If an account with that email exists, we've sent a password reset link. Please check your inbox.","requestFailed":"Failed to process your request. Please try again.","unexpectedError":"An unexpected error occurred. Please try again.","Invalid email address":"Please enter a valid email address"},"ResetPasswordPage":{"title":"Reset Password","subtitle":"Enter your new password","newPassword":"New Password","confirmPassword":"Confirm Password","resetting":"Resetting...","resetPassword":"Reset Password","successMessage":"Your password has been reset successfully. You can now sign in with your new password.","redirecting":"Redirecting to sign in...","missingToken":"No reset token provided. Please check your email for the correct link.","resetFailed":"Password reset failed. The link may have expired or is invalid.","unexpectedError":"An unexpected error occurred. Please try again.","backToForgotPassword":"Request New Link","passwordMust":"Password must:","passwordMin":"be at least 8 characters long","passwordLetter":"contain at least one letter","passwordNumber":"contain at least one number","passwordSpecial":"contain at least one special character","confirmPasswordRequired":"Please confirm your password","passwordsMustMatch":"Passwords must match","hidePassword":"Hide password","showPassword":"Show password"},"ChangePasswordCard":{"title":"Change Password","description":"Update your account password","currentPassword":"Current Password","newPassword":"New Password","confirmPassword":"Confirm Password","changing":"Changing...","changePassword":"Change Password","successMessage":"Your password has been changed successfully.","changeFailed":"Failed to change password. Please check your current password.","unexpectedError":"An unexpected error occurred. Please try again.","passwordMust":"Password must:","passwordMin":"be at least 8 characters long","passwordLetter":"contain at least one letter","passwordNumber":"contain at least one number","passwordSpecial":"contain at least one special character","currentPasswordRequired":"Current password is required","confirmPasswordRequired":"Please confirm your new password","passwordsMustMatch":"Passwords must match","hidePassword":"Hide password","showPassword":"Show password"},"PaymentProcessingPage":{"errorTitle":"Payment Processing Error","tryAgain":"Try Again","processingTitle":"Processing Your Payment","processingMessage":"We're activating your subscription. This usually takes just a few seconds.","pleaseWait":"Please don't close this window.","takingLonger":"This is taking longer than expected. Please wait a bit longer..."},"TrendsPage":{"title":"Trends","description":"Track your AI-SEO performance over time","timeRanges":{"1m":"Last Month","3m":"Last 3 Months","6m":"Last 6 Months"},"summaryCards":{"visibilityTrend":{"title":"Visibility Trend","tooltip":"Average visibility score trend"},"optimizationTrend":{"title":"Optimization Trend","tooltip":"Technical AI-SEO score trend"},"sentimentTrend":{"title":"Sentiment Trend","tooltip":"Positive sentiment trend"},"issuesTrend":{"title":"Issues Trend","tooltip":"Critical issues trend"}},"charts":{"seoScores":{"title":"SEO Score Trends","description":"Visibility & Optimization over time","visibilityScore":"Visibility Score","optimizationScore":"Optimization Score"},"sentiment":{"title":"Sentiment Distribution","description":"Brand sentiment over time","positive":"Positive","neutral":"Neutral","negative":"Negative"},"issues":{"title":"Technical AI-SEO Issues","description":"Issues by severity","critical":"Critical","optimizable":"Optimizable"},"competitive":{"title":"Competitive Position","description":"Market share trends","topCompetitor":"Top Competitor Share","totalCompetitors":"Total Competitors"}},"emptyState":{"title":"Not Enough Data","message":"Trends require at least 2 reports. After your first report, new reports are automatically generated every 2 weeks. You'll receive an email notification when each report is ready. Check back here once your second report arrives!","action":"View Dashboard"},"errorState":{"title":"Failed to Load Trends","message":"Please try again later.","action":"Retry"},"loadingState":{"message":"Loading trends data..."}},"emails":{"verification":{"subject":"Verify your email address - GAISEO","preview":"Verify your email address for GAISEO","heading":"Welcome to GAISEO!","greeting":"Hi {name},","body":"Thank you for signing up for GAISEO. To complete your registration, please verify your email address by clicking the button below:","buttonText":"Verify Email Address","footer":"This link will expire in 24 hours. If you didn't create an account with GAISEO, you can safely ignore this email."},"passwordReset":{"subject":"Reset your password - GAISEO","preview":"Reset your GAISEO password","heading":"Reset Your Password","greeting":"Hi {name},","body":"We received a request to reset your password for your GAISEO account. Click the button below to create a new password:","buttonText":"Reset Password","footer":"This link will expire in 1 hour. If you didn't request a password reset, you can safely ignore this email. Your password will remain unchanged."},"reportReady":{"subject":"Your GAISEO Report is Ready","preview":"Your AI-SEO analysis report is ready to view","heading":"Your GAISEO Report is Ready!","greeting":"Hi {name},","body":"Great news! Your AI-SEO analysis report has been completed and is now ready for review. Click the button below to view your comprehensive AI-SEO insights and recommendations:","buttonText":"View Your Report","footer":"If you have any questions about your report or need assistance, please don't hesitate to contact our support team."}}},"now":"$undefined","timeZone":"UTC","children":["$","$L3",null,{"parallelRouterKey":"children","error":"$undefined","errorStyles":"$undefined","errorScripts":"$undefined","template":["$","$L4",null,{}],"templateStyles":"$undefined","templateScripts":"$undefined","notFound":[[["$","title",null,{"children":"404: This page could not be found."}],["$","div",null,{"style":{"fontFamily":"system-ui,\"Segoe UI\",Roboto,Helvetica,Arial,sans-serif,\"Apple Color Emoji\",\"Segoe UI Emoji\"","height":"100vh","textAlign":"center","display":"flex","flexDirection":"column","alignItems":"center","justifyContent":"center"},"children":["$","div",null,{"children":[["$","style",null,{"dangerouslySetInnerHTML":{"__html":"body{color:#000;background:#fff;margin:0}.next-error-h1{border-right:1px solid rgba(0,0,0,.3)}@media (prefers-color-scheme:dark){body{color:#fff;background:#000}.next-error-h1{border-right:1px solid rgba(255,255,255,.3)}}"}}],["$","h1",null,{"className":"next-error-h1","style":{"display":"inline-block","margin":"0 20px 0 0","padding":"0 23px 0 0","fontSize":24,"fontWeight":500,"verticalAlign":"top","lineHeight":"49px"},"children":404}],["$","div",null,{"style":{"display":"inline-block"},"children":["$","h2",null,{"style":{"fontSize":14,"fontWeight":400,"lineHeight":"49px","margin":0},"children":"This page could not be found."}]}]]}]}]],[]],"forbidden":"$undefined","unauthorized":"$undefined"}]}] </article></body></html>