hasmun.

Services

Technical SEO

Fix the crawl, speed, and structure problems capping your rankings.

Search engines can only rank what they can crawl, render, and understand. That sounds obvious, but it is the single most common blind spot for small business websites. You can have excellent content and a growing backlink profile and still underperform in search because something technical is quietly getting in the way.

Technical SEO is not glamorous, and it rarely shows up in a screenshot the way a new blog post or a press mention does. But it is the foundation everything else sits on. A content strategy built on top of a site with indexation problems, or a link-building campaign pointed at pages Google cannot properly render, is effort spent on a structure that cannot hold it.

What's included

Site speed and Core Web Vitals, explained plainly

Core Web Vitals are a set of metrics Google uses to measure real user experience: how quickly your page becomes usable, how stable the layout is while it loads, and how responsive it feels when someone interacts with it. Slow, janky pages create a worse experience, and Google factors that into rankings, particularly in close competitive matchups.

For small business sites, the most common culprits are unoptimized images, bloated page builder plugins, too many third-party scripts (chat widgets, tracking pixels, review widgets all loading at once), and cheap or oversold hosting. Fixing this usually does not mean rebuilding your site. It means finding and removing the specific things slowing it down.

Crawl and indexation fixes

Before anything else can rank, a page has to be crawled and indexed. We check for common blockers: an accidentally misconfigured robots.txt file, a stray noindex tag left over from a staging site, orphaned pages with no internal links pointing to them, and crawl budget wasted on low-value pages like filtered or parameterized URLs that multiply endlessly on e-commerce sites in particular.

We also fix redirect chains and canonical issues, which happen when a site has moved, been redesigned, or changed URL structures over time without cleaning up after itself. A page that redirects three or four times before landing, or two pages competing for the same keyword because neither has a canonical tag pointing to the other, both quietly dilute your rankings.

Structured data and what it can and cannot do

Structured data, or schema markup, is a standardized way of labeling content so search engines understand exactly what it represents: a product, a review, a local business, a frequently asked question, an event. It is what enables rich results like star ratings, price ranges, or FAQ dropdowns to appear directly in search results.

It is worth being clear about what schema does not do. Adding structured data does not directly boost your rankings on its own, and no legitimate provider should promise that it will. What it does is make your existing content eligible for richer, more clickable search results, which can meaningfully improve your click-through rate even at the same ranking position.

Site architecture and internal linking

How your pages are organized and linked to each other affects both how search engines understand your site and how they distribute authority across it. A flat, logical structure where important pages are just a click or two from the homepage tends to perform better than a deep, disorganized one where key pages are buried.

Internal linking is one of the most underused levers small businesses have, because it is entirely within your control and costs nothing to fix. Linking from your highest-authority pages to the pages you most want to rank, using descriptive anchor text, is a direct way to pass along ranking signal you are already generating elsewhere on your own site.

Common technical debt in small business sites

Sites built on WordPress often accumulate plugin bloat over years, with multiple tools doing overlapping jobs and each adding its own scripts and stylesheets. Sites on platforms like Shopify, Wix, or Squarespace have less flexibility to fix certain technical issues directly, which means the fixes have to work within what the platform allows.

Platform migrations, whether a full replatform or a routine redesign, are one of the most common sources of technical debt. URL structures change, old pages get orphaned or lost, and redirects are often handled hastily or not at all. If your traffic dropped around the time of a redesign or migration, that is almost always the first place to look.

Mobile-first indexing and why it changes what matters

Google predominantly uses the mobile version of your site, not the desktop version, to determine rankings, even for searches performed on a desktop computer. This means if your mobile site hides content, has different navigation, or renders differently than your desktop site, the mobile version is effectively the one that counts.

For small business sites this often surfaces as tap targets that are too small or close together, text that is too small to read without zooming, or content that gets cut off or hidden behind accordions and tabs in a way that limits how much of it search engines give weight to. We check the mobile experience directly rather than assuming a responsive design automatically solves this.

JavaScript rendering and why some modern sites underperform

Sites built with heavy JavaScript frameworks can look perfectly normal to a visitor while being difficult for search engines to fully render and understand, particularly if important content or links only appear after client-side scripts run. This is an increasingly common issue as more small business sites move to modern page builders and app-like frameworks without accounting for how that affects crawlability.

We check whether your content and links are actually visible in what search engines render, not just what a browser shows a human visitor, and identify where server-side rendering or static generation would meaningfully improve how your site gets indexed.

HTTPS and security as a baseline ranking signal

A valid, properly configured HTTPS certificate has been a baseline expectation for years, and its absence, or mixed content that loads some resources over an insecure connection, is treated as a trust issue by both browsers and search engines. We check for this along with more subtle issues, like certificates that are correctly installed on the main domain but missing on subdomains.

This category also includes making sure your site is not compromising crawl efficiency by accidentally serving both HTTP and HTTPS versions of the same pages as separate, indexable URLs, which splits ranking signal between two versions of what should be one page.

Working within the limits of your specific platform

Not every technical fix is available on every platform, and part of doing this work well is knowing the difference upfront rather than recommending changes that are simply impossible to make. On a custom-coded site, nearly everything is fixable directly. On WordPress, most fixes are achievable through a combination of configuration, careful plugin choices, and, when necessary, direct code changes.

On hosted platforms like Shopify, Wix, or Squarespace, some technical decisions, like URL structure or certain redirect behaviors, are controlled by the platform itself and cannot be changed no matter who is doing the work. In those cases, we focus on what is actually achievable within the platform: theme-level performance improvements, structured data the platform allows you to add, and site architecture decisions you do control, like collection and navigation structure, rather than promising fixes the platform will not permit.

For larger or higher-traffic sites, we also look at crawl budget more directly, meaning how search engines allocate their limited crawling activity across your site, and identify where that budget is being wasted on low-value pages instead of the pages you actually want indexed and updated quickly.

Monitoring after the initial round of fixes

Technical SEO is not something you fix once and leave alone. A plugin update can silently reintroduce a slowdown that was already solved. A developer adding a new page template can accidentally skip the canonical tag every other template includes. A CDN or hosting change can affect how quickly pages load in ways that never show up until Core Web Vitals data catches it weeks later.

We set up ongoing monitoring for the issues most likely to recur: crawl errors and coverage problems in Search Console, Core Web Vitals scores over time, and spot checks after any significant site change, whether that is a redesign, a new plugin, or a platform update, so a new problem gets caught in days rather than discovered by accident months later when rankings have already slipped.

Frequently asked questions

Do I need a developer for this work?

Some fixes require developer access to your site's code or hosting environment, particularly on custom-built sites. Many others, especially on platforms like WordPress or Shopify, can be handled without a developer. We will tell you upfront which is which for your specific site.

Will technical changes break or slow down my site during the work?

Changes are made carefully and tested, and higher-risk changes are staged or scheduled during low-traffic periods where possible. The goal of technical SEO is to reduce risk to your site's performance, not introduce it.

How is this different from an SEO plugin like Yoast?

Plugins like Yoast are useful for basic on-page checks such as meta tags, but they do not fix crawl budget issues, redirect chains, Core Web Vitals problems, or structural issues in how your site is organized. They flag a narrow slice of what technical SEO actually covers.

Does switching website platforms improve SEO on its own?

Not by itself, and a poorly executed migration can actively hurt your rankings for months. If a platform is genuinely limiting what you can fix, that is worth discussing, but the migration itself needs to be planned around SEO, not treated as an afterthought.

How often does technical SEO need attention?

It is not a one-time task. A thorough pass at the start catches the accumulated issues, but ongoing monitoring matters because new issues get introduced by redesigns, plugin updates, content changes, and platform updates over time.

My site feels fast when I load it. Could it still have a speed problem?

Yes, often. Your own experience is usually on a fast connection, a cached browser, and a powerful device, none of which represents a typical visitor. Core Web Vitals are measured from real user data across a range of devices and connections, which is why a site can feel fast to its owner and still score poorly.

Can technical SEO fix rankings on its own, without content or links?

It removes obstacles, but it does not create demand where none exists. A technically flawless page with thin content targeting the wrong keywords still will not rank well. Technical work is necessary but usually not sufficient on its own.

Will fixing technical issues cause a temporary drop before things improve?

It can, occasionally, particularly with major structural changes like a URL restructure, since search engines need time to recrawl and re-evaluate the new setup. We flag any change with that kind of risk in advance so it is never a surprise.

How do you measure whether the fixes actually worked?

Through a combination of re-crawling the site to confirm issues are resolved, monitoring Core Web Vitals scores over time, and tracking indexation and crawl stats in Google Search Console to confirm search engines are picking up the changes.