Indexability checker for search engines and AI tools

The Indexability Checker covers signals that affect whether search engines and AI tools can discover, crawl, and index your important pages. TXT Files validates robots.txt and llms.txt, Main Page surfaces canonical and alternate signals, Link Crawler contributes page-level robots access signals, and Sitemap Monitoring contributes sitemap coverage signals. Review each signal in the feature view where it is collected, alongside the Link Crawler and Main Page Analyzer details that provide its context.

Uptime affects SEO by keeping your pages reachable for search engine crawlers and real users. A brief outage may not cause an immediate ranking change, but repeated downtime can interrupt crawling, reduce trust in page availability, waste crawl opportunities, and create poor user signals when visitors land on errors. Uptime monitoring helps you detect access problems quickly, including timeouts, unexpected status codes, and missing expected content. For marketers, this matters most on high-value pages such as campaign landing pages, product pages, checkout flows, and content that receives frequent organic traffic. WebPixie pairs uptime checks with multiple check attempts and cross-location verification on paid plans to reduce false positives before alerting your team. For search visibility, combine uptime checks with the Indexability Checker and Link Crawler to catch blocked pages, broken links, and crawlability issues.

Yes. The Indexability Checker validates and analyzes robots.txt and llms.txt line by line, giving each file a valid or invalid result and flagging syntax it cannot parse. This lives in the TXT Files view, where you can see how a directive is interpreted instead of guessing whether a rule is written correctly. It also checks whether a sitemap is referenced in robots.txt, so a missing reference is visible during review. On the Main Page view, WebPixie surfaces the canonical URL and alternates as supporting visibility signals rather than a standalone indexing verdict. Indexability signals contribute to the WebPixie Site Score without requiring you to inspect each technical finding manually. For link-level crawl health, pair it with the Link Crawler, and compare plan limits on the pricing page.

WebPixie alerts you when a monitored page becomes unreachable or fails the conditions you configured. No monitoring tool can guarantee that a search engine has not attempted to crawl during an outage, but fast detection helps reduce the duration and SEO risk of availability problems. Uptime monitoring checks for timeouts, connection failures, unexpected status codes, redirects, and missing expected content, then uses multiple check attempts and cross-location verification on paid plans to reduce false positives before opening an incident. Alerts are sent by email on every plan, with Slack and webhooks available on eligible plans, so the right team can act quickly. Confirmed outages can be tracked through incident management, including severity, affected resource, and closure timing. For search-specific risk, combine outage alerts with the Indexability Checker to catch crawl-blocking configuration problems.

They answer different questions. The Link Crawler is about link health: starting from your homepage it follows discovered public internal links and reports each checked link's status code, response time, redirect status, and whether it loads successfully, while also listing the outbound links each page points to without checking them. The Indexability Checker is about crawl signals: it validates robots.txt and llms.txt, reports robots.txt sitemap-reference presence, uses canonical and alternate signals from the Main Page view, and includes crawler-derived robots-disallowed tags. A link can be healthy yet blocked from search engines, and a page can be visible to crawlers yet link to broken destinations, so the two signals do not replace each other. The crawler deliberately ignores robots.txt while following links, because it must fetch a page to confirm it works; search eligibility is reviewed through indexability signals instead. Many teams run both and compare plan limits on the pricing page.

The Indexability Checker only reports whether a Sitemap: directive is present in your robots.txt, a presence check. Sitemap Monitoring goes further: it actually fetches the declared sitemap tree, walks supported sitemap indexes down to leaf files, and catalogs declared URLs with lastmod, changefreq, and priority when present. It also cross-checks sitemap coverage against the Link Crawler, flagging crawled internal links that are missing from your sitemap. Sitemap Monitoring is available on Starter and above, while the robots.txt presence check is included on every plan; compare plans on the pricing page.