The sitemap at www.loadmill.com/sitemap.xml lists 27 URLs, and every one of them is on loadmill.lovable.app, the site builder's hosted address, which only redirects back to www.loadmill.com. robots.txt points crawlers to the sitemap on that same host. The file lists /blog but none of the 52 posts, including the nine mobile testing articles published since April 2026. Five older posts, among them the Loadmill and Postman comparison, live on URLs with spaces and colons, and that comparison shows an application error instead of the article. Search engines and AI assistants are being handed a map of a different site, with the content that earns search traffic left off it.
First action
Open www.loadmill.com/sitemap.xml and robots.txt, replace loadmill.lovable.app with www.loadmill.com in both, and submit the sitemap in Google Search Console.
How to measure it
Indexed pages in Search Console
- Now
- –
- Target
- All 27 site pages and all 52 posts submitted and indexed
- By
- 45 days
Steps
Correct the host
Change every sitemap entry and the robots.txt Sitemap line from loadmill.lovable.app to www.loadmill.com, then resubmit in Search Console.
Web developer 2 hours
Repair the five broken URLs
Give the five posts whose URLs contain spaces and colons clean slugs, add permanent redirects from the old addresses, and confirm the Postman comparison loads.
Web developer 1 day
Build the generator
Inputs: the route list and the blog post index (slug, publish date, last edit). Output: sitemap.xml with www URLs and lastmod, rebuilt on every publish.
Web developer 3 days
Add canonical tags
Each page and post declares its own www.loadmill.com address, so the builder host is never treated as the original.
Web developer 1 day
Build the nightly check
Fetch every sitemap URL; flag redirects, error text, missing titles or the homepage default title; send a summary to the marketing channel.
Web developer 2 days
Approve and switch on
A person reviews the redirect list and the first generated file, then the publish hook goes live.
Marketing lead 1 hour
Measure
Track submitted versus indexed pages and blog clicks in Search Console each week for six weeks.
Marketing lead weekly
Why it works
Fix the three files by hand this week, then replace the hand-kept sitemap with a small automation. The build reads two inputs, the site's route list and the blog's post index, and writes sitemap.xml on every publish with www.loadmill.com URLs, a lastmod date per page and every post included. A nightly check fetches each URL in the sitemap, confirms it returns the article and not an error or a redirect, confirms the page title is not the homepage default, and posts a short report to the marketing channel. The five posts with spaces in their URLs get clean slugs and permanent redirects from the old addresses. A person approves the redirect list and the first generated sitemap before it goes live; after that it runs on its own and only raises exceptions.
A sitemap is the cheapest signal a site sends about which pages matter. When every entry points to a host that redirects, crawlers have to guess, and new posts wait to be discovered through links alone. The blog is Loadmill's main source of search content and none of it is listed. Fixing the map costs days, and generating it removes the chance of it drifting again when the next page or post ships.
Ready to use
ChecklistSitemap and blog URL repair list
[ ] sitemap.xml: every loc on https://www.loadmill.com [ ] robots.txt: Sitemap line on https://www.loadmill.com/sitemap.xml [ ] All 52 blog posts listed with lastmod [ ] Five posts with spaces or colons in the URL moved to clean slugs [ ] Permanent redirects from the five old addresses [ ] Postman comparison post loads and has its own title [ ] Canonical tag on every page and post [ ] Sitemap resubmitted in Google Search Console and Bing Webmaster Tools [ ] Nightly check reports to the marketing channel
Risks and how to handle them
Old blog URLs are linked from other sites
Use permanent redirects from every old address and keep them in the nightly check.
The site builder regenerates the old sitemap on the next deploy
Make the generator part of the publish step and let the nightly check flag any entry on the wrong host.
Evidence
- Your websiteSitemap (checked twice on November 16, 2026): www.loadmill.com/sitemap.xml lists 27 URLs and every one is on the host loadmill.lovable.app, not www.loadmill.com; that host answers with a 302 redirect to www.loadmill.com. The file has no lastmod dates and includes /blog but none of the individual blog posts.Source
- Your websiterobots.txt (checked November 16, 2026) allows all crawlers and ends with the line "Sitemap: https://loadmill.lovable.app/sitemap.xml", so the only sitemap search engines are pointed to sits on a different host from the live site.Source
- Your websiteBlog index: 52 posts from January 2019 to August 2, 2026, nine of them published between April and August 2026 on AI mobile testing agents; no newsletter signup. Five posts from 2022 to 2024 have URLs containing spaces and colons, including the Loadmill and Postman comparison, which returned "Unexpected Application Error!" with the homepage title instead of the article when fetched on November 16, 2026. The last product update post is dated October 30, 2025.Source