silkra

Issue reference

The registry behind the Issues panel: every active finding, its pillar, severity, evidence type, and meaning.

Badge guide

  • CriticalHighest-priority finding, usually tied to access, indexing, or a broken page.
  • WarningA problem worth reviewing that may affect quality or performance.
  • InfoA lower-priority observation that adds context rather than urgency.
  • CheckA deterministic result from parsed HTML, crawl data, or a counted value.
  • SignalA model-derived observation from similarity, fit, or content analysis.

106 of 106 issues

Technical

IssueSeverityEvidenceWhat it means
Broken Page (4xx Error)CriticalCheckThis page returns an error like 404 Not Found. Visitors and search engines can't access it.
Canonical Points ElsewhereCriticalCheckThis page's canonical tag points to a different URL, telling Google to index that page instead. This effectively blocks this page from search results. If intentional, great — if not, this page is invisible.
Could Not Reach PageCriticalCheckThis page couldn't be accessed. The server may be down, the URL may be wrong, or there's a network issue.
Page Timed OutCriticalCheckThis page didn't respond in time. The server may be overloaded or the page may be stuck.
Server Error (5xx)CriticalCheckThis page is returning a server error. Something is broken on the backend.
Sitemap URL returns errorCriticalCheckThis URL is in the sitemap but returns a 4xx/5xx status code. Search engines waste crawl budget on a dead URL and may distrust the entire sitemap.
Blocked by RobotsWarningCheckThis page is blocked from search engines by a robots directive. Google can't crawl or index it.
Canonical HTTP/HTTPS MismatchWarningCheckThe canonical tag uses a different protocol (HTTP vs HTTPS) than this page. This can confuse search engines about which version to index.
Canonical WWW/Non-WWW MismatchWarningCheckThis page is served on one host but its canonical tag points at the same URL on the other www variant. Search engines treat www and non-www as separate sites, so ranking signals get split between the two.
Content Requires JavaScriptWarningCheckMost of this page's content does not exist in the raw HTML — it only appears after JavaScript runs. Google usually renders JS (with delays); many AI crawlers and most scrapers read the raw response only, so for them this page is nearly empty. Measured, not inferred: we compared the raw response against the rendered page.
Hreflang Missing SelfWarningCheckThis page has hreflang tags for other languages but doesn't include itself. Google requires each page to reference itself in hreflang.
Missing Canonical TagWarningCheckNo canonical tag found. Without one, search engines decide which version of this URL to index when duplicates exist (from parameters, trailing slashes, HTTP/HTTPS variants, etc.).
Missing Language DeclarationWarningCheckThis page doesn't declare its language. Screen readers won't know how to pronounce the content, and Google may not serve it to the right audience.
No Semantic HTML ElementsWarningCheckThis page uses no semantic HTML at all — no <main>, <article>, <nav>, <section>, <header>, <footer>, and no ARIA landmark roles. The entire document is anonymous containers, so machines (search extractors, screen readers, AI crawlers) cannot tell the content from the chrome.
Not Secure (HTTP)WarningCheckThis page is served over HTTP instead of HTTPS. Browsers show security warnings, and Google prefers secure sites.
Page Blocked from GoogleWarningCheckThis page has a noindex tag telling Google not to show it in search results. If that's intentional, great. If not, it's invisible to searchers.
Page Too LargeWarningCheckThis page is over 3 MB. Large pages load slowly, especially on mobile networks.
Redirect ChainWarningCheckThis URL goes through multiple redirects before reaching the final page. Each redirect adds load time and loses a bit of link value.
Sitemap URL has canonical elsewhereWarningCheckThis URL is in the sitemap but its canonical tag points to a different URL. The sitemap is advertising a non-canonical version, which dilutes equity signals.
Sitemap URL is noindexWarningCheckThis URL is included in the sitemap but flagged noindex. The sitemap says "index this", the page says "don't index this" — search engines treat the conflict as a low-quality signal.
Sitemap URL redirectsWarningCheckThis URL is in the sitemap but redirects to another URL. Search engines waste crawl budget hitting the redirect hop instead of the final destination.
Slow PageWarningCheckThis page took over 3 seconds to respond. Slow pages frustrate visitors and can hurt rankings; past 5 seconds most visitors leave before it loads.
No FaviconInfoCheckThis site has no favicon. The browser tab will show a generic icon, which looks unprofessional.
Not in SitemapInfoCheckThis page isn't in your XML sitemap. Google will still find it through links, but including it in the sitemap helps ensure it gets crawled regularly.

On-Page

IssueSeverityEvidenceWhat it means
Missing Title TagCriticalCheckThis page has no title tag. Google will auto-generate one — and it rarely matches what you'd choose. Pages without titles also see lower click-through rates in search results.
Duplicate H1WarningCheckAnother page has the same H1 heading. This signals to search engines that these pages may cover the same topic, diluting ranking signals.
Duplicate Meta DescriptionWarningCheckAnother page shares the same meta description. This is a missed opportunity — each page should have a unique snippet to differentiate it in search results.
Duplicate Schema TypesWarningCheckThis page has multiple JSON-LD blocks declaring the same schema type. This can confuse search engines about which one is authoritative and may trigger Search Console warnings.
Duplicate TitleWarningCheckAnother page on this site has the exact same title tag. Search engines may struggle to determine which page to rank, leading to keyword cannibalization.
Images Missing Alt TextWarningCheckOver 30% of images on this page don't have alt text. Screen readers can't describe them, and Google can't understand what they show.
Missing H1 HeadingWarningCheckThis page has no H1 heading. The H1 is the primary headline that tells Google, visitors, and screen readers what the page is about. Without it, there's no clear content anchor.
Missing Meta DescriptionWarningCheckNo meta description found. Google will auto-generate a snippet from page content — often pulling text that doesn't represent the page well.
Title Too ShortWarningCheckThis title is under 30 characters. Short titles miss opportunities to include keywords and attract clicks.
Title Will Be Cut OffWarningCheckThis title is too wide and will be truncated in Google search results. Measured in pixels (the way Google actually truncates); when pixel data is unavailable, a 65-character fallback applies.
Excessive Schema BlocksInfoCheckThis page has more than 10 JSON-LD blocks. Too many schema blocks add page weight and can indicate auto-generated or redundant markup.
H1 Too LongInfoCheckThis H1 heading is over 70 characters. Long headings lose visual impact, often get truncated in templates, and may indicate keyword stuffing rather than a clear, scannable label.
Heading Levels SkipInfoCheckHeading levels on this page skip (e.g. an H2 followed by an H4 with no H3). Not a ranking factor, but outline parsers, screen readers, and content chunkers reconstruct the document structure from heading order — skipped levels flatten or scramble that outline.
Incomplete Social TagsInfoCheckThis page has some Open Graph tags but is missing the title, description, or image. Social shares won't look as good.
Meta Description Will Be Cut OffInfoCheckThis meta description is too wide and will be truncated in search results. Measured in pixels; when pixel data is unavailable, a 160-character fallback applies.
Multiple H1 HeadingsInfoCheckThis page has more than one H1. This is valid HTML5 and Google has confirmed it is not a ranking problem — flagged only as a structure note, since a single clear top-level heading can make the page hierarchy easier to scan. Often just a template artifact (e.g. a logo and the post title both marked up as H1).
No Breadcrumb SchemaInfoCheckThis page doesn't have breadcrumb markup. Breadcrumbs can appear in search results and help users understand where the page fits in your site.
No Schema MarkupInfoCheckThis page has no structured data. Schema markup helps Google understand your content and can enable rich results like star ratings, FAQs, and breadcrumbs in search.
No Social Media TagsInfoCheckThis page has no Open Graph tags. When shared on Facebook, LinkedIn, or other platforms, it won't have a proper preview.
No Social Share ImageInfoCheckThis page has no og:image tag. When shared on social media, it won't have a preview image.
No SubheadingsInfoCheckThis page has content but no H2 subheadings. Subheadings break up text, make it easier to scan, and help Google understand the page structure.
Title Leads with Site NameInfoCheckThis title leads with the site or brand name, pushing the page-specific words to the end. Searchers scan left-to-right, so the most descriptive words usually work harder up front.
Too Many HeadingsInfoCheckThis page has over 50 headings. That usually means heading tags are being used for styling instead of structure.

Content

IssueSeverityEvidenceWhat it means
Cannibalization RiskWarningSignalThis page's content vector is nearly identical (≥0.96 similarity) to another page in the same semantic group — competing near-duplicates inside one topic, not classic keyword overlap across different angles. Diffuse/template groups and Ungrouped leftovers are excluded at the source; passage-level clones are covered by the duplicate-content rule instead.
Content Over 2 Years OldWarningCheckThis content hasn't been updated in over 2 years. Freshness matters more for some topics (news, pricing, product docs) than others (evergreen references).
Exact Duplicate ContentWarningCheckAnother crawled URL serves byte-identical main content (same content hash). Exact copies split link equity and force search engines and AI systems to pick a winner — usually inconsistently.
Important Page With Thin ContentWarningCheckThis page has high internal importance but fewer than 300 words. The site is funneling authority to a page with little substance.
Low Unique ContentWarningCheckLess than 30% of this page is unique versus site chrome (nav, footer, sidebars). This is a boilerplate signal — not the same as cross-page duplicate passages.
Mostly BoilerplateWarningCheckOver 80% of this page is shared template content (navigation, footer, sidebar). There's very little unique content here.
Page Belongs to a Duplicate Content SetWarningCheckMost of this page's passages also appear on other pages (shared-content share ≥ 70). That clone-tier overlap usually means doorway or mirrored content competing with itself — distinct from mid-band template blocks that are expected on catalog sites.
Pages Share Repeated PassagesWarningSignalA large share of this page's passages are repeated across five or more other pages — the "every post ends with the same 300-word pitch" pattern. The repeated material dilutes what makes each page distinct, for both readers and retrieval systems scoring passage uniqueness.
Section Drifting Into BoilerplateWarningCheckOne site section carries far more template/boilerplate content than the rest of the site — its pages are mostly repeated markup with a thin unique layer. Measured against this site's own baseline, not a generic threshold, so it points at a specific template drifting, not "the site has templates".
Staleness Concentrated in Key PagesWarningCheckThe site's highest-value pages are markedly older than its low-value ones — freshness effort is going to pages that matter least. This is a prioritization finding, not a page count: it compares the dated high-value cohort's age against the rest of the site.
Text Buried in CodeWarningCheckVisible text is under 10% of the remaining markup (script and style payloads already excluded), and the extracted body is still thin. This is markup burying the content — not just a JavaScript-heavy stack.
Thin ContentWarningCheckThis page has fewer than 300 words of substance. On editorial sites that often means the page cannot stand on its own; on template or programmatic sites, short pages may be intentional.
Title Promises What Body Doesn't DeliverWarningSignalThe title reads as semantically distant from the page content (embedding-measured). Searchers and AI systems select this page based on the title's promise — when the body doesn't deliver it, the result is pogo-sticking and misrouted retrieval.
Topics Drift Across PageWarningSignalThis page's passages disagree with each other — the body wanders across topics instead of staying on one clear subject. Retrieval and summarization both struggle when a page is several articles in one URL.
Video-only thin pageWarningCheckPage hosts video but has < 200 words of supporting text. AI / search engines have nothing to index, summarise, or cite.
Low-Value PageInfoSignalThis page scores below the content-value threshold on a model-derived composite (pagination, archives, tag pages, feeds, and similar scaffolding usually land here). It is usually structural support, not a standalone content target — treat the score as an observation, not a verdict.
No Published DateInfoCheckNo published or modified date could be found on this page. Without date signals, search engines can't assess content freshness — a key E-E-A-T factor.
Outlier in Semantic GroupInfoSignalThis page is in a semantic group but sits far from the group centroid — it does not share much semantic ground with its siblings. In a tight topic group that may mean a misfit or thin page; in a loose group it is less meaningful.

Architecture

IssueSeverityEvidenceWhat it means
Noindex Page With Inbound EquityCriticalCheckThis page is set to noindex but receives 3+ internal links from elsewhere on the site. Every one of those links pours authority into a URL that Google has been told to ignore — the equity is actively leaking out of your indexed pages.
Authority Flows In, Not OutWarningCheckA site section holds a large share of internal authority (PageRank from internal links) but its pages barely link onward in their body content — link equity enters the section and stops there instead of routing to other pages that could use it.
Body links external onlyWarningCheckPage has in-body links but every one points to an external domain. No internal authority is being passed through editorial copy.
Broken Outbound LinksWarningCheckThis page links to one or more URLs that return an error (HTTP 4xx/5xx). Visitors hit dead ends and crawl equity is wasted on broken targets. Only counts targets that were crawled in this session — out-of-scope or external uncrawled URLs are not flagged.
Buried Deep in SiteWarningCheckThis page sits 4+ clicks from the homepage and has little internal inbound support. Depth alone is not always a problem — deep but well-linked docs can be fine — but a deep, under-linked page is easy for users and crawlers to miss.
Dead End PageWarningCheckThis page has no internal links to other pages on your site. Visitors hit a dead end, and link equity can't flow to the rest of your site.
Hub Page With Thin ContentWarningCheckThis page acts as a hub in your site architecture (many pages link to and from it) but has very little content. Hub pages should be strong, authoritative landing areas.
Important But InvisibleWarningCheckThis is a high-value page (pageValue ≥ 0.7) but almost nothing on your site links to it and it sits 3+ clicks from the homepage. The site is treating one of its best assets as if it were a footnote — readers and crawlers will struggle to find it.
Isolated Within Semantic GroupWarningSignalThis page appears to have little or no linking to other pages in its own semantic group (intra-group isolation, based on model-derived grouping). Distinct from a site-wide orphan — the page may still be linked from elsewhere on the site.
Linked Only From NavigationWarningCheckEvery internal link pointing here comes from navigation, footer, or sidebar templates — no other page links to it editorially from body content. Template links carry weak endorsement; the site's prose never vouches for this page.
Links Without TextWarningCheckSome links on this page have no anchor text (like image links without alt text). Google can't understand what these links are about.
No Links in Body ContentWarningCheckAll links on this page live in navigation, header, or footer chrome. There are no editorial links inside the main content (parsed from mainContentMarkdown). In-body links pass significantly more SEO weight than boilerplate nav links.
No Outbound LinksWarningCheckThis page has no unique outbound links — internal or external. Visitors and crawlers have nowhere to go from here, and any inbound equity stops on the page.
Not Anchored in Site StructureWarningCheckLink-graph analysis shows this page is not embedded in the site's structure the way hubs and spokes are — either classified as a structural orphan, or receiving zero inbound internal links despite belonging to a topic group.
Not Linking to Closest Related PageWarningSignalThis page has a clear closest semantic neighbor elsewhere on the site, but the body never links to it. That is a missed internal link — readers and crawlers lose an obvious related path.
Orphan PageWarningCheckNo other page on your site links to this one. Google and visitors may never find it.
Placeholder Links Never Filled InWarningCheckThis page has in-body links whose href is an unfinished placeholder — a bare social or video domain root (e.g. youtube.com/ with no path), "#", or an empty href. The anchor text usually promises something specific while the link goes nowhere useful. These are template links someone forgot to fill in.
Redirect with inbound equityWarningCheckPage is a redirect but receives ≥ 3 internal links — internal authority is pointing at a redirect hop instead of the final destination.
Thin Bridge PageWarningCheckThis page acts as a connector between semantic groups in your site graph but has fewer than 300 words. Bridge pages route both readers and link equity across topics — when they're thin, the connection is fragile and authority leaks instead of flowing through.
Too Many LinksWarningCheckThis page has over 500 links. Google may not follow all of them, and it can look spammy.
Body links all genericInfoCheck≥ 80% of in-body links use generic anchor text ("here", "click here", "read more", etc.). Editorial copy is missing entity-rich anchor signals.
Generic Link TextInfoCheckThis page uses vague link text like "click here" or "read more". Descriptive anchor text helps Google understand what the linked page is about.
High body anchor densityInfoCheckIn-body links are very dense (more than 1 link per 20 words). Reads as spammy or affiliate-style copy and dilutes individual link value.
Links Won't Pass ValueInfoCheckThis page has a nofollow directive, so links from here won't pass any ranking value to the pages they link to.
Many External LinksInfoCheckThis page has over 100 external links. That's a lot of ways to leave your site, and it dilutes the value of each link.
Many Nofollow LinksInfoCheckOver 30% of links on this page are nofollow. Nofollow should be used sparingly for untrusted or paid links, not as a default.
Single in-body link targetInfoCheckAll in-body links on this page point to the same internal URL. Suggests a single-CTA / funnel structure that misses opportunities for related-content discovery.
Very Few Internal LinksInfoCheckThis page has fewer than 3 internal links. More internal links help visitors discover related content and help Google understand your site structure.

AI Search

IssueSeverityEvidenceWhat it means
AI Crawlers BlockedWarningCheckYour robots.txt blocks AI crawlers like GPTBot, ClaudeBot, or PerplexityBot. This prevents your content from appearing in AI-powered search results and answers.
Answer Content Buried DeepWarningSignalThis page contains answer-shaped content — stats, definitions, Q&As, or step lists — but its most representative passage sits deep in the body while the lead is weaker framing. Retrieval systems and skimming readers quote leads; the answers exist, just not where they get found.
Best Passage Buried DeepWarningSignalThe passage that best represents this page sits deep in the body. Retrieval systems may still find it, but readers and lead-biased scrapers meet weaker framing first — the answer exists, just not up front.
Content Only Partially RecoveredWarningSignalThis page shows substantial visible text, but Silkra retained only a small share of it as page-specific content, and the markup independently lacks a clear content boundary. Worth verifying what parsers actually see here — search snippets, reader modes, and AI retrieval may be working from a fragment of the page.
Extraction May Have Missed the Main ContentWarningCheckThe page body holds substantial text, but main-content extraction captured under 20% of it — the extracted "content" may be the navigation shell rather than the page itself. Worth verifying what parsers see here: search snippets, AI retrieval, and this tool's own content metrics could be reading the wrong part of the page.
Lead Drifts From BodyWarningSignalThe opening passage reads as semantically distant from the rest of the page (embedding-measured, evidence attached). Readers and retrieval systems both use the lead to set context — when it drifts, both lose the thread.
Markdown extraction failedWarningCheckPage has substantial HTML but we couldn't pull any usable main content markdown. AI tools, RSS readers, and search snippets all break here — they get a page they can't read.
Wall of TextWarningCheckThis page has very long paragraphs (150+ words average). Both readers and AI systems struggle with dense, unbroken text.
FAQ Page Without FAQ SchemaInfoCheckThis page reads like a genuine FAQ (several question/answer pairs were detected) but declares no FAQPage/QAPage schema. Adding it helps engines and LLMs parse the Q&A structure cleanly.
First chunk too shortInfoCheckFirst retrievable chunk is < 30 words. AI assistants often retrieve only the first chunk — too short means weak grounding for snippet / citation use.
Missing llms.txt FileInfoCheckYour site doesn't have an /llms.txt file. This emerging standard tells AI systems which content they can use for training and retrieval.
No Main Content LandmarkInfoCheckThis page has semantic elements but no <main> or role="main" — nothing declares which part of the document is the primary content. <article> groups a piece of content; it is not a landmark. Extractors fall back to heuristics, and assistive tech loses its "skip to content" anchor.
No Recognizable Content ContainerInfoCheckMain-content extraction found no semantic container (<main>, <article>, or a recognizable content selector) and had to clean the raw <body> instead. Silkra recovered the content, but every parser reading this page — AI crawlers, reader modes, snippet extractors — has to guess where the content is. On high-value pages this guessing costs the most.