Centous sells technical SEO and "crawler-friendliness", but its own sitemap sends Google to 35 blog addresses at the site root, and every one fails: 33 show a 404 and 2 a server error. The posts live at /blog/<post>/, with no redirect from the old address. So Google is told the articles do not exist, and any old link or bookmark to them breaks. The new lead generation intern will be sending prospects to this content, and right now search engines cannot reach it.
First action
Change the sitemap generator to the /blog/ path and deploy.
How to measure it
Indexed blog posts
- Now
- –
- Target
- 33 of 33
- By
- 30 days
Steps
Fix generator
Sitemap uses the /blog/<post>/ path.
Frontend Developer (Next.js) 2 hours
Add redirects
301 from each root address to its /blog/ page.
Frontend Developer (Next.js) 2 hours
Fix the two errors
Repair or retire posts that fail at both addresses.
Frontend Developer (Next.js) 2 hours
Resubmit
Sitemap in Search Console; request indexing of the top ten posts.
Marketing Lead 1 hour
Check internal links
Homepage and service pages link to /blog/ addresses.
Frontend Developer (Next.js) 1 hour
Monitor
Weekly status check of every sitemap URL.
Frontend Developer (Next.js) weekly
Use in outreach
Link working articles in the intern's sequences.
Lead generation Intern ongoing
Why it works
Generate the sitemap from the same source as the blog routes so posts appear at /blog/<post>/; add permanent (301) redirects from every old root address to its /blog/ page; fix or retire the two posts that error at both addresses; resubmit the sitemap in Google Search Console and request indexing of the top ten posts. Add a weekly check that every sitemap URL returns 200.
Posts that return 404 drop out of search, and redirects recover the value of links built up over the years. It is also the clearest proof an SEO and development agency can offer: its own site has no broken pages.
Ready to use
ChecklistSitemap repair list
[ ] Sitemap lists /blog/<post>/ for all posts [ ] 301 from every old root address [ ] Two failing posts repaired or retired [ ] Sitemap resubmitted in Search Console [ ] Top ten posts submitted for indexing [ ] Internal links point to /blog/ [ ] Weekly 200-status check
Risks and how to handle them
Redirect loops
Test every redirect once after deploy.
Lost posts
Restore from the WordPress backend before retiring any post.
Evidence
- Your websiteSitemap (70 URLs, checked November 4, 2026): all 35 blog posts are listed at root addresses such as /nest-js-vs-express-js/; 33 of them return "404" and 2 return a server error. The same posts load at /blog/<post>/ (33 of 35), with no redirect from the listed address. Only the 35 service and company pages in the sitemap work.Source
- Your websiteFooter newsletter sign-up ("Join our Newsletter and get interesting stuff and updates"); social profiles on LinkedIn, X, Facebook and Instagram; a GoodFirms profile linked under Recognitions; Marketing services list "Technical SEO" covering "Website indexing compatibility, crawler-friendliness".Source
- HiringCareers page, two open roles: a Lead generation Intern to "Kickstart your career in B2B lead generation" by "researching potential clients, building prospect databases, and supporting LinkedIn and email outreach for IT services"; and a Senior Shopify Developer with "3+ years" in theme customization and JavaScript, where "Hands-on experience with Shopify Markets, Checkout Extensibility, and B2B functionalities is required".Source
- Your websiteBlog: four listing pages from three authors; recent posts on Shopify semantic search and generative AI (February 2026), Shopify Plus vs traditional B2B platforms and WooCommerce checkout tips (January 2026), and a guide to reconfiguring GTM and Google Analytics after the Shopify checkout upgrade.Source