Both robots.txt and sitemap.xml tell search engines the site lives at http://localhost:3000, which is a developer's own machine and not reachable from outside. All 96 sitemap URLs point there, including the 14 service pages, 7 case studies, 4 blog posts and 58 job posts. A site: search on November 19, 2026 returned no pages from krissdevhub.dev. A five-month-old domain with few links relies on its sitemap for Google to discover pages, so for now the studio's best proof, the case studies, is invisible to search.
First action
Set the site URL variable in the Vercel production environment to https://www.krissdevhub.dev and redeploy.
How to measure it
Indexed pages out of 96
- Now
- –
- Target
- 80+
- By
- 30 days
Steps
Fix the base URL
Set the production site URL used by app/sitemap and app/robots to https://www.krissdevhub.dev.
Frontend Engineer (React / Next.js) 30 minutes
Clean robots.txt
Remove the Host line and point Sitemap at https://www.krissdevhub.dev/sitemap.xml.
Frontend Engineer (React / Next.js) 15 minutes
Check the head tags
Confirm canonical, og:url, og:image and JSON-LD on three page types use the live domain.
SEO Specialist 1 hour
Verify and submit
Verify the domain in Search Console and Bing Webmaster Tools and submit the sitemap.
SEO Specialist 1 hour
Request indexing
Homepage, six service pages and seven case studies first.
SEO Specialist 1 hour
Guard the build
Fail the deploy if sitemap.xml or robots.txt contains "localhost".
Frontend Engineer (React / Next.js) 1 hour
Watch coverage
Review indexed pages and crawl errors weekly for a month.
SEO Specialist weekly
Why it works
Set the production base URL that the Next.js sitemap and robots routes read (usually one environment variable in the Vercel production settings) to https://www.krissdevhub.dev, redeploy, and confirm that both files list the live domain. Remove the Host line, since Google ignores it. The same base URL usually feeds canonical tags, og:url, Open Graph images and JSON-LD, so check those on the homepage, a service page and a case study. Then verify the domain in Google Search Console and Bing Webmaster Tools, submit the sitemap, and request indexing for the homepage, the six service pages and the seven case studies. Finally, add a check to the deploy pipeline that fails the build if "localhost" appears in sitemap.xml or robots.txt, so it can't come back.
The rest of the marketing plan (SEO, content, vertical pages, job listings) depends on Google being able to find the pages. This is a one-line configuration fix, and it unlocks all 96 URLs at once.
Ready to use
ChecklistCrawl fix checklist
[ ] Production base URL = https://www.krissdevhub.dev [ ] robots.txt: no Host line; Sitemap: https://www.krissdevhub.dev/sitemap.xml [ ] sitemap.xml: 96 URLs on https://www.krissdevhub.dev [ ] Canonical, og:url, og:image, JSON-LD checked on /, /services/mvp-development, /case-studies/medscript-ai [ ] Search Console + Bing verified, sitemap submitted [ ] Indexing requested for top 14 pages [ ] Build fails if "localhost" appears in sitemap or robots
Risks and how to handle them
Canonical tags also point to localhost and keep pages out of the index
Check the rendered head of three page types before submitting the sitemap.
Thin pages get indexed but don't rank
Prioritise case studies and service pages, which have the most specific content.
Evidence
- Your websiterobots.txt (checked November 19, 2026): "Host: http://localhost:3000" and "Sitemap: http://localhost:3000/sitemap.xml".Source
- Your websiteSitemap (checked twice on November 19, 2026, on www and the bare domain): all 96 URLs start with "http://localhost:3000" instead of https://www.krissdevhub.dev and share one build-time lastmod; it lists 14 service pages, 7 case studies, 4 blog posts and 58 job posts, and no industry pages. A site: web search the same day returned no pages from krissdevhub.dev.Source
- HiringSEO Specialist (contract): keyword research for founders and developers and audits of "schema tags, page speed, and metadata" with Search Console, Semrush and Ahrefs, requiring an "understanding of crawler logic". Technical Content Writer (contract): case studies on Next.js, Postgres and LLM choices from interviews with tech leads, plus tutorials.Source