SEO Isn't Just Marketing's Job: A QA Intern's Look at Sitemaps and Robots.txt
Of everything I tested during my internship, SEO analysis was the part I expected the least, and learned the most from. It turns out a QA tester can catch problems that quietly hurt a business's visibility on Google, long before marketing ever notices.
Starting with robots.txt
My first step on any site was simply visiting its robots.txt file. It sounds almost too basic to matter, but this file tells search engines what they're allowed to crawl, and getting it wrong can accidentally hide an entire website from Google without anyone realizing it.
Then came the sitemap
Checking sitemap.xml turned out to be where the real bugs were hiding. On Garden Sewa's site, I found several issues that had nothing to do with buttons or forms:
- Duplicate URLs -both /partners and /partnership existed in the sitemap, creating duplicate content that confuses search engine crawlers.
- Inconsistent priorities -service subpages were split between 0.80 and 0.64 priority with no clear logic behind the difference.
- Misplaced priorities -utility pages like privacy policies and terms of service shared the exact same priority score as key landing pages like services and projects, telling search engines to treat a legal disclaimer as important as a page that actually drives business.
- Identical timestamps -nearly every URL listed the exact same last-modified date, down to the millisecond, a strong signal to search engines that the site is never actually updated.
Small details, real business impact
The "identical timestamps" bug in particular stuck with me. It's invisible to a regular visitor, nobody browsing the site would ever notice it, but to a search engine, it can mean the difference between a page getting recrawled regularly or getting quietly deprioritized over time. That's the kind of bug you'd never find by just clicking through pages as a user; you have to know to go looking for it.
Checking the basics, on-page
Beyond the sitemap, I also got into the habit of inspecting a page's <title>, <img> alt text, <h1>, and meta description using the browser's inspect tool. These elements don't affect whether a button works, but they affect whether the page shows up correctly, or at all, in search results.
Why QA should care
A perfectly functioning website that search engines can't index properly, or won't bother recrawling, is still failing its users. They just never get the chance to find it in the first place. Once I understood that, SEO checks stopped feeling like a separate discipline and started feeling like just another layer of quality.
The takeaway
Good QA doesn't stop at what a user can see and click. Some of the most consequential bugs live in files most users will never open.
