SEOLivly
Menu
Home Tools Blog Services Contact Run the free scan

Technical SEO checklist for a small site with no developer

By Derek Murphy  · 

A technical SEO checklist for a small site is not a shorter version of an enterprise audit. It is a different list. A site with forty pages and one person maintaining it does not need log file analysis or crawl budget modelling. It needs to know which pages Google can see, which URLs it is telling Google to ignore by accident, and what breaks every time the site is edited.

I run this list on small sites before any content work, because a new post published onto a page with a noindex tag is a week of writing thrown away. The order matters: indexability first, then the plumbing that controls it, then speed, then the extras.

Step one: can the page be indexed

Fetch the page with the website auditor and read the head. Check for a meta robots noindex, an X-Robots-Tag header, a canonical that points somewhere else, and a status code that is not 200. Those four checks catch the failures that make everything else pointless. On a small site the usual cause is a staging setting that was never turned off, or an SEO plugin that added a noindex rule to a whole post type.

Do the same check on the pages that matter most: the homepage, the main service page and the newest post. If one of them fails, stop and fix it before reading the rest of the list. There is no technical fix that outweighs a page that is not allowed into the index.

Step two: the canonical and the redirects

The canonical should be the URL you want indexed, written as an absolute URL, in the same form as the sitemap entry. Check the trailing slash, the www and the http version. A canonical that points at a redirect is a page asking to be filed under a URL that does not resolve, and a canonical that differs from the sitemap starts an argument Google resolves by ignoring both.

Then look at the redirects. One hop from an old URL to the new one is fine. A chain of three is wasted requests and a slow response. Internal links should point at the final URL, not the old one, because every click now starts with a redirect. Redirects are also the easiest place to lose a page during a migration, so keep a list of what points where.

Step three: sitemap and robots

The sitemap is a promise. Every URL in it should return 200, have a self-referencing canonical and be a page you would want in a search result. If the sitemap builder includes tag archives, search pages or media attachments, trim it. A small site usually needs one sitemap with the real pages in it, not an index of six files.

Robots.txt should declare the sitemap and block only what you do not want crawled. The two rules I see broken most: blocking the whole site while trying to block a test folder, and leaving a rule that blocks JavaScript, CSS or images, which stops the page rendering properly for a crawler. Fetch the file and read it line by line rather than trusting the plugin screen.

Step four: speed and mobile

You do not need a perfect speed score. You need the page to answer in a reasonable time on a phone, which comes down to four things: server response time, image weight, the number of render-blocking scripts in the head, and layout shift from images without dimensions. The scan reports the parts it can see, and the crawl budget walkthrough explains why the server side matters more than the score.

Test on a phone, on a normal connection, with the cache off. A page that loads in a second on your laptop can take five on a train. If the theme loads four font files, six tracking scripts and a slider, the page speed problem is a template decision, not a content decision.

Step five: structured data and the small stuff

If the site has JSON-LD, validate it. Broken JSON-LD does not help and can block rich results, and a block that describes something the page does not show is worse than no block. Add markup only to page types you actually understand: the organization or local business, the article, the breadcrumb. The rest can wait.

Then the small items that still cost. One H1 per page. Alt text on images that carry meaning. A viewport tag. Clean URLs with words in them. A contact page with a real address or a working form. None of these will transform a site, and all of them are easy to fix while the file is open.

The monthly twenty-minute pass

  1. Run the scan on the homepage, the main service page and the last two posts.
  2. Check that every URL in the sitemap still returns 200. Spot check ten.
  3. Read robots.txt once. It changes less often than people fear, which is why a stray edit persists.
  4. Open each page on a phone and check that the title, the H1 and the first paragraph are readable without zooming.
  5. Look at the pages that changed this month and confirm the canonical and title survived the edit.

That pass catches almost everything a small site experiences, because a small site changes slowly. The failures come from edits, plugin updates and an old test folder, not from a crawler decision you cannot influence.

When to call a developer

Some items are not yours to fix. Server response time, HTTPS certificates, redirects at the host level and anything that needs a config file belong to the host or a developer. Know which ones those are before you start, so the checklist does not become a week of work you cannot finish. The scan tells you what is wrong. Who fixes it is a separate decision, and the service page covers the cases where it should be me. The tools hub has the checkers for the parts you can do yourself.

Check your own page

The free website auditor runs forty checks on one URL and lists the worst problems first. No signup. If you would rather hand the list to somebody, the fix service has the prices on the page.

Run the free scan

Keep reading