Website structure and performance may affect whether search engines can discover and crawl pages, as well as those pages’ search visibility. However, navigation design or slow loading alone cannot establish why visibility has declined. The historical Semrush article discussed here identifies insufficient internal links, duplicate URLs generated by faceted navigation, and slow server responses as areas worth checking. The following summarizes the risks it highlights and the author’s observations. These are not current search engine rules, nor are they sufficient to determine a particular website’s actual performance.
Deeper Content Also Needs Internal Links
On large e-commerce sites and blogs, pagination can mean readers need more clicks to reach deeper content from the homepage. The article recommends checking click depth and looking for opportunities to add internal links if a large amount of unindexed content takes five, six, or even ten or more clicks to reach from the homepage. These figures describe situations worth investigating, not thresholds beyond which content will not be indexed.
- Check whether content can only be reached by working through pages one at a time.
- Check whether category pages, tag pages, author pages, and links within articles provide alternative entry points.
For example, if a large collection of articles is linked only through the blog homepage and a few category pages, it is worth checking whether older content lacks other entry points. However, that alone does not establish why the content has not been indexed.
Faceted Navigation: Consider Query Relevance as Well as Duplicate URLs
Faceted navigation lets users filter by attributes such as size and color. The article suggests that it can also help crawlers find content, but poor design may create crawler traps, crawl budget issues, and duplicate content problems.
For example, the same list of red, size 10 shoes may appear at multiple URLs simply because the URL parameters are arranged differently. Access through internal search and category navigation may also create different paths. Restricting filtering options comes at a cost, though. The author warns that it may exclude pages that match specific queries and could otherwise rank, leaving only pages that are less relevant to those queries. Therefore, “more restrictions are better” is not a universal solution.
JavaScript and Large Menus Are Worth Checking, but Are Not Necessarily Problems
The historical article warns that navigation relying entirely on JavaScript may make crawling more difficult, leaving deeper pages without crawlable entry points. This warning reflected risks at the time; it does not establish that all JavaScript websites have problems today.
The author also recommends that sites already experiencing crawling issues check whether their large menus generate substantial amounts of code, even if developers consider the implementation SEO-friendly. The point is to check whether the implementation is related to the crawling problem, rather than assume that a large menu impedes visibility.
Speed May Affect Visibility, but Slow Sites Will Not Necessarily Disappear from Search
The author says he has seen slow loading affect the search visibility of specific pages or page types, but has not personally seen an entire site disappear from Google or Bing as a result. He does not rule out that possibility, either. The article also warns that an unresponsive or slow server may affect rankings and visibility. These are the author’s experiences and assessments of risk, not grounds for concluding that “slow sites will inevitably disappear.” Evaluating an individual website still requires relevant speed, crawling, and search performance data; the material discussed here provides no such case-specific evidence.
Website structure and performance: perspectives from across the web
What approach should be used to handle faceted navigation?
There is no single solution that works for every website. The historical Semrush article lists options including canonical tags, meta tags, robots.txt, nofollow on internal links, and hiding links, but emphasizes choosing based on the individual case. Any assessment should also consider that restricting filtering options may reduce the number of highly specific pages eligible to rank. This historical list is not a set of current configuration rules.
What should you watch for when an entire website is built with JavaScript?
Beyond checking menus, examine whether other parts of the website also rely on JavaScript in ways that make content difficult for search engines to discover. The historical Semrush article suggests that an entirely JavaScript-based website may have crawling issues that extend beyond its menus. This was a warning about risks at the time, not a basis for concluding that all such websites have problems today. Individual implementations still need to be checked.
Is looking only at search rankings enough when evaluating website speed?
Rankings should not be the only consideration. In addition to discussing search visibility, the Semrush article’s author says he has seen slow loading affect a page’s ability to convert visitors into leads or sales. Therefore, even when investigating search issues, it may be useful to monitor conversion performance as well. However, the author’s experience does not prove that speed caused a decline in conversions on any particular website.
References
- SMB Issues: Why Isn’t My Website Showing Up on Google?www.semrush.com · 2016-12-30T17:30:00Z — Discusses: What approach should be used to handle faceted navigation?; What should you watch for when an entire website is built with JavaScript?

