A website audit can uncover broken links, duplicate content, images that slow loading, navigation problems, and missing internal links. It can also reveal buttons that work but lack visual cues that they are clickable. Fixes need to suit the website: the ecommerce case below involved copy, images, and menus, while the Tailwind v4 case required changes to button styles. These audits differ in scope, so findings from part of a site should not be treated as a diagnosis of the whole site. Making the same changes elsewhere does not guarantee the same results.
A Shopify store with declining traffic and conversions: checking content, speed, and navigation together
In a case featured by Semrush, Michael Ryan’s team worked with a Shopify store experiencing sustained declines in traffic and conversions. The team spent about three weeks examining SEO, conversion paths, and technical performance, covering product page templates, the checkout experience, speed, and site structure.
- Duplicate content on category pages: Fixes included rewriting page copy and cleaning up metadata.
- Uncompressed images slowing page loads: The team compressed the images to address loading problems.
- Missing internal links between blog posts and product pages: The team also reorganized the menus to address navigation and linking issues.
The case reported a 27% increase in organic search sessions, a 9% increase in average order value, and a 14% increase in conversion rate within six weeks. These results followed the full set of changes to that site. The available information does not show how much each fix contributed, and the results are not a growth guarantee for other stores.
Spot-checking a large website: address errors first, but do not mistake a sample for the full picture
The 2014 Samsung example involved a crawl of only 100 URLs. It revealed 65 broken internal links, 18 broken external links, sitemap errors, six pages missing meta descriptions, and six pages with duplicate content. Based on the report’s classifications at the time, the author recommended fixing these errors before addressing warnings.
The warnings included 38 images missing ALT attributes, some pages with too many links or H1 headings, title length issues, and loading problems. For image-heavy websites, the author also recommended reviewing performance and tags, as well as optimizing images. This example lists issues and the order in which to address them, but does not explain how to carry out each fix or report the results of completed repairs. The tool’s classifications at the time should not be equated with current search engine rules.
A Tailwind v4 website: clickable does not mean all the cues are in place
A Search Engine Journal author examined the nohacks.co homepage and one representative article page and found that native buttons for the menu, subscription, playback, and back-to-top functions lacked a pointer cursor. The article noted that Tailwind v4 removed the default button pointer styling present in v3. If that styling is not restored after an upgrade, keyboard, screen reader, and click functionality can still work, but the cursor cue changes.
The fix is to set cursor: pointer in the base layer of the global styles for enabled button elements and elements with role set to button. Exclude natively disabled elements so they retain their existing disabled cursor styles. This fix addresses only a visual cue; it does not establish that the entire site has passed an accessibility audit.
Website audits: perspectives from across the web
What should you do if there are too many navigation links or pages are buried too deep?
Start by reviewing how the navigation and content are actually used, reducing rarely used menu links and making important content easier to find. In one 2019 case, the menu contained more than 400 links, and some content was as many as 15 pages away from the homepage. The author recommended keeping content within three clicks of the homepage wherever possible. However, this was the author’s recommendation for site structure, not an official rule that applies to every website.
How can you identify issues missed during website migration planning?
Regularly crawl the website before and after migration and compare the results to identify issues that may have been missed during planning and URL mapping. Then use longer-term historical records to check for broader changes. This method, proposed in a 2014 article, can help pinpoint problems, but the article does not describe specific fixes or the results of completed repairs for a migration case.
References
- How To Perform a Quick SEO Audit with Semrushwww.semrush.com · 2014-12-01T13:00:28Z — Discusses: How can you identify issues missed during website migration planning?
- Google’s Agent-Friendly Checklist Is The Accessibility Audit Restatedwww.searchenginejournal.com · 2026-06-12T09:00:35+00:00 — Source used in the article above.
- 7-Step Ecommerce Website Audit to Boost Conversionswww.semrush.com · 2024-05-14T08:30:00Z — Source used in the article above.
- How To Untangle the Website Architecture of a Site with 500,000+ Pageswww.semrush.com · 2019-07-10T07:00:00Z — Discusses: What should you do if there are too many navigation links or pages are buried too deep?

