Technical SEO advice tends to split into two piles. One is about content — keywords, topics, writing better than the competition. The other is about speed.
Between them sits a layer almost nobody discusses with site owners, largely because it is invisible: how your pages are structured, what machine-readable information they emit, and whether search engines can efficiently reach everything you publish.
That layer is almost entirely your theme’s doing. You can write the best article in your category and have it undermined by template code you have never seen.
Here is what to look for, in the order it matters.
Speed is the other half of this story, and it has its own post. This one covers everything that is not performance.
Layer 1: Semantic structure
Search engines read your page as a document with a hierarchy, not as a picture. That hierarchy comes from HTML elements, and themes routinely get it wrong because they are designed visually.
The heading problem. Headings exist to describe document structure. In many themes they are used to control size. The symptoms:
- The site name marked as the top-level heading on every page, so your actual page title is demoted
- Multiple top-level headings on one page because several sections needed large text
- Levels skipped — a main heading followed by a fourth-level one — because that size looked right
- Buttons, prices, or sidebar labels marked as headings
The fix is conceptual, not cosmetic: one top-level heading per page describing what the page is about, then a logical descent. Size should be a styling decision applied to the correct level, not the reason a level was chosen.
The element problem. A page built entirely from generic containers is harder to interpret than one using real navigation, main content, article, aside, and footer elements. This also determines how screen readers move through your page, which is why structure and accessibility keep turning out to be the same conversation.
How to check: view the page outline using a browser extension or your browser’s accessibility inspector. If the outline does not read like a sensible table of contents for the page, the theme is misrepresenting your content.
Layer 2: Structured data
Structured data is a machine-readable summary embedded in the page: this is a product, this is its price, this is whether it is in stock, this is the author and publication date, this is the review score.
It is what produces the enhanced search results — star ratings, prices, FAQ expansions, breadcrumb trails — and increasingly it is also what helps AI-driven answer surfaces describe your business correctly rather than guessing from prose.
What a decent theme should emit, depending on type: organisation or local business details, article markup on posts, product markup with price and availability, breadcrumb markup, and FAQ markup where you have genuine question-and-answer content.
The four common failures:
- Missing entirely. Nothing is emitted, so you appear as a plain result while competitors show ratings and prices.
- Duplicated and conflicting. The theme emits product markup and your SEO plugin emits its own, describing the same page slightly differently. This is more common than missing markup and harder to notice.
- Incomplete. Required properties absent, so the markup exists but does not qualify for enhanced display.
- Stale or hard-coded. Values baked into the template rather than pulled from your content — a product marked in stock permanently, a review score that never changes, an organisation name left from the demo.
How to check: run your key page types through Google’s Rich Results Test and a general schema validator. Do a homepage, a product or service page, a blog post, and a category page. Errors here are usually fixable and usually the theme’s responsibility.
Layer 3: Crawlability and architecture
This is where structural mistakes get expensive, because they affect whether pages get discovered at all.
Click depth. How many clicks from the homepage to your deepest page? Pages buried five or six levels down get crawled less and treated as less important. If your theme’s navigation only exposes top-level categories and everything else is reachable only through pagination, you have created depth.
Orphan pages. Pages nothing links to. They exist, they may be in your sitemap, and they perform poorly because nothing on the site indicates they matter. Themes create orphans when they drop related-content modules or when a landing page is published outside the navigation and never linked.
Internal linking volume. Related posts, breadcrumbs, category listings, and contextual links inside content all pass signals between your pages. A theme that removes related-post sections in favour of a cleaner design has quietly cut a large portion of your internal linking.
Pagination. A frequent and serious failure. If your blog archive or product listing uses infinite scroll or a “load more” button with no crawlable links to the underlying pages, everything past the first screen may be effectively invisible. Whatever the interaction looks like to a human, real links to paginated pages need to exist in the markup.
Faceted navigation. The eCommerce-specific version, and the biggest crawl problem in the category. Filters that generate a unique URL for every combination — colour plus size plus price plus brand plus sort order — can produce an effectively unlimited set of near-identical pages. Crawlers spend their time on those instead of your actual products. The theme’s filtering implementation decides whether this happens, and whether those URLs are properly canonicalised or excluded.
Duplicate URLs. The same content reachable at several addresses: with and without a trailing slash, with and without a www prefix, under multiple category paths, through tag and author archives that duplicate your post listings, or through attachment pages that exist for every uploaded image. Each is a small dilution, and themes vary widely in how they handle them.
Layer 4: Metadata control
Small layer, easy to check.
Does the theme let you control the title tag and meta description per page — or does it generate them and fight your SEO plugin for control? Duplicate or conflicting meta tags are a real symptom of theme-plugin overlap.
Also check social sharing metadata. Post one of your URLs into a private chat and look at the preview card. If it shows the wrong image, no image, or the theme author’s demo text, the metadata is not configured. That card is your first impression on every share, and it is set in template code.
Layer 5: Images
Images sit across SEO, accessibility, and performance, and the theme controls most of it.
- Alt text support. Does the theme actually output alt attributes, including for images placed through page builder modules? Builder-placed images are a common gap.
- Responsive image handling. Multiple sizes offered so phones download phone-sized files.
- Lazy loading, applied correctly. Off-screen images should defer. The main above-the-fold image should not, because lazy-loading your hero delays exactly the element being measured for loading performance. Themes get this backwards regularly.
- Modern formats, with sensible fallbacks.
A twenty-minute audit
Run this on your own site:
- Check the heading outline on your homepage, a key service or product page, and a blog post.
- Run those three through the Rich Results Test.
- Click from your homepage to your deepest content and count the clicks.
- Load your blog or product archive with JavaScript disabled and see whether links to page two exist.
- Search your own site for a page you know exists and check whether anything links to it.
- Post a URL into a chat and inspect the preview card.
- Try reaching the same page through two different paths and see whether the URL differs.
Anything broken here is a theme issue in most cases, which means it applies site-wide and is worth raising with the theme author before you spend another month on content.
What to ask before buying
Four questions that separate studios who thought about this from studios who did not:
- What structured data types does the theme output, and can I turn them off if my SEO plugin handles them?
- How is pagination implemented, and are paginated pages crawlable without JavaScript?
- For store themes: how do filter URLs behave, and are they canonicalised or excluded from indexing?
- Does the theme generate title tags and meta descriptions, or defer to an SEO plugin?
A studio with good answers will answer immediately. A studio that has not considered it will talk about speed instead.
The point
Content earns rankings. Structure decides whether that content is understood, reached, and represented properly — and structure is bought, not written.
It is worth knowing what you bought.
At eThemeStudio, we treat semantic structure and structured data as build requirements rather than plugin territory, and we document exactly what each theme emits so it does not collide with your SEO stack. Want us to run the twenty-minute audit on your current site? Send us the URL.
Comments (0)