Sitefire's most original asset is its own research: a 13,500-post study showing that structure alone flags AI-written posts with a score of 98.0 out of 100. The post's main call to action is to play Spot the Slop, and llms.txt lists Spot the slop and Slop Checker as Sitefire's research for AI agents. All three tool pages (/slop-checker, /deslop and /spot-the-slop) return 404 Not Found, and they are still in the sitemap. Readers, journalists and the AI crawlers Sitefire helps customers win all reach a dead end at the moment of highest interest.
First action
Decide which of the three tools should be live, and redeploy or redirect the others today.
How to measure it
Tool-sourced trials
- Now
- –
- Target
- 40 a month
- By
- 60 days
Steps
Find the cause
Check why the three routes return 404 and whether the tools still exist in the codebase.
Founder & CTO 1 hour
Restore or redirect
Redeploy the live tools and 301 any retired route to the closest live one.
Founder & CTO 1 day
Clean the files
Make the sitemap and llms.txt list only working tool URLs.
Founding Product Engineer 1 hour
Build the hand-off
Checker result, then "Fix this with Sitefire", then a trial with that page as the first brief.
Founding Product Engineer 3 days
Link it everywhere
From the study, the blog index, the homepage footer and the docs.
Founder & CEO 1 day
Watch every sitemap URL
A daily check that alerts the team when any listed URL stops returning 200.
Founder & CTO 2 hours
Measure
Tool uses, trial clicks and trials started each week.
Founder & CEO weekly
Why it works
This week, restore the three pages, or 301-redirect any retired tool to the live one. Then make the Slop Checker the free first step: a visitor pastes a URL and gets the structural score, the two features that give the post away, and a "Fix this with Sitefire" button. That button starts the trial with the page loaded as the first improvement brief. Spot the Slop stays as the shareable game. Link all three from the study, the blog index, the homepage footer and llms.txt, and take anything that stays retired out of the sitemap.
The study gives people a reason to visit, and the checker gives them a reason to sign up. Any marketer worried that AI content is penalized has a question the tool answers in seconds, and the answer leads straight to Sitefire's paid product, which writes and improves articles. Dead URLs in the sitemap and llms.txt also tell crawlers the site is not maintained, which is the opposite of what a GEO vendor needs to show.
Ready to use
ChecklistResearch tools relaunch list
[ ] /slop-checker, /deslop and /spot-the-slop return 200 (or 301 to a live tool) [ ] Sitemap lists only live tool URLs, with lastmod [ ] llms.txt Research section links working pages [ ] Slop study CTA tested end to end [ ] "Fix this with Sitefire" passes the URL into the trial [ ] Result is cached and shareable by link [ ] Daily check on every sitemap URL [ ] Trials tagged by source tool
Risks and how to handle them
Each check costs model calls
Cache results per URL and limit anonymous checks per day.
A score reads as an accusation
Present it as structure advice, not a verdict on who wrote the post.
Evidence
- Your website"How to Tell AI Slop From Human Writing" (September 2026): 13,500 blog posts analyzed; structure alone separated AI from human posts with a score of 98.0 out of 100; the main call to action is to play the five-round "Spot the Slop" game; no author is named on the post, although the underlying SlopShape study is credited to Sitefire's CEO, with a public verification repository.Source
- Your websiteResearch tools: /slop-checker, /deslop and /spot-the-slop all returned "404 Not Found" on repeated checks on November 10, 2026 (also on the www host), although all three are listed in the sitemap.Source
- Your websitellms.txt (the file written for AI agents): describes Sitefire as a GEO platform; lists a "Research" section with "Spot the slop" and "Slop Checker"; lists one case study (Pointhound, not Jerry); no plan prices and no comparison pages.Source
- Your websiteSitemap (53 URLs, checked November 10, 2026): 13 blog posts, 2 case studies, 27 docs pages (including CMS guides for WordPress, Webflow, Framer and dotCMS), pricing, contact and legal pages, plus /slop-checker, /deslop and /spot-the-slop with no lastmod. No comparison, industry, use-case or German-language pages. Seven blog posts first published between January and April share one lastmod, 2026-07-29.Source