Our services
If you can think it, we can make it brainsoft.
If you can think it, we can make it brainsoft.
A small business site usually has one job: show up when someone nearby searches for what you sell. Most of the sites I audit are not failing because of keywords. They fail on plumbing. A stray noindex tag, a redirect chain three hops long, a mobile layout that shifts as the page loads. Search engines crawl these things constantly and quietly decide your site is more trouble than it is worth.
Here is the checklist I run through on a small site, in order, from cheapest fix to most involved. It assumes one domain, a handful of templates, and no dedicated SEO team. Budget a day for the technical pass and a couple of hours a month for monitoring. If you would rather hand the crawl-and-fix loop to someone who does it weekly, our services cover exactly this kind of work.
Before touching anything else, check that a bot can reach your pages. Open the site with JavaScript disabled in the browser. If you see a blank shell, you have a rendering problem, and no amount of on-page work will help until it is fixed. Then check robots.txt and the meta robots tag on a live page.
curl -s https://example.com/robots.txt
curl -s https://example.com/ | grep -i 'name="robots"'
A staging site that was copied to production often keeps its Disallow: / line. I have seen that single line cost a business a full quarter of organic traffic.
Pick one hostname and one trailing-slash convention, then make everything else redirect to it with a single 301. Chains like http to https to www to the final URL waste crawl budget and dilute signals. Check the raw headers rather than trusting the browser address bar.
curl -sIL http://example.com/about | grep -iE '^(HTTP|location)'
Every page should carry a self-referencing canonical tag. If your CMS generates paginated archives or filter URLs, either canonicalise them to the clean page or block them in robots.txt. Do not do both to the same URL set.
An XML sitemap is not a ranking factor, but it shortens the time between publishing and indexing. Generate it from your content source, not by hand, and keep it under 50,000 URLs per file. Reference it from robots.txt with an absolute URL.
User-agent: *
Allow: /
Disallow: /admin/
Sitemap: https://example.com/sitemap.xml
Only include pages you want indexed. A sitemap full of 404s and redirects is a signal that your site is unmaintained.
If your product pages are a client-side React app with no server rendering, Google may eventually index them, but other crawlers and social preview bots will not. For a small business site the fix is usually boring: server-render the marketing pages, keep the interactive bits client-side. Static generation is fine. So is a traditional template engine. What matters is that the HTML response already contains the title, the body copy and the internal links.
Check for duplicates first. A CMS that appends the business name to every title produces pages like "Contact Us | Acme | Acme". Then check length and uniqueness:
h1 per page, matching the visible headlineIf two pages target the same intent, merge them. Small sites rarely have a content volume problem; they have a duplication problem.
LocalBusiness, Organization, Product, FAQPage and BreadcrumbList are the ones that pay off for a small site. The rule is simple: mark up what a visitor can see. Prices in JSON-LD that do not appear in the HTML get ignored or, worse, trigger a manual action. Validate with the Rich Results Test before you deploy, and keep the markup in the template so it cannot drift from the content.
Test on a throttled connection, not your laptop on fibre. The three metrics that matter are LCP, INP and CLS. In practice the fixes are: compress and correctly size images, set explicit width and height attributes to stop layout shift, preload the hero font, and cut third-party scripts you cannot justify. A chat widget and three analytics tags will cost you more than any image optimisation.
Verify the domain property, not just the URL prefix, so http, https, www and non-www are covered. Submit the sitemap once. Then check the Pages report weekly for a month: 404s, soft 404s, crawled-but-not-indexed and duplicate-without-user-selected-canonical are the four buckets that matter. Fix them in that order. Set up a simple uptime check too, because a site that is down during a crawl is invisible.
Do the full pass once, then repeat the crawl and Search Console checks monthly. Re-run the rendering and Core Web Vitals steps whenever you change templates, add a third-party script, or move hosting. Template changes are where most regressions come from.
No. Search Console, the Rich Results Test, PageSpeed Insights and a free crawler such as Screaming Frog in its 500-URL mode cover everything here. Paid tools mostly save time on large sites; a small business site fits comfortably inside the free limits.
You can still control titles, descriptions, canonicals, sitemaps, image sizes and redirects through the platform settings. If the platform cannot serve server-rendered HTML or set a canonical tag, that is a hard limit and worth weighing against a rebuild. Get in touch if you want a second opinion on whether a migration is justified.