Technical Checklist: Speed, SSL, Mobile, Broken Links
Technical problems are the ones visitors never see directly, but they feel the effects immediately: a slow page they abandon, a security warning that scares them off, a broken link that dead-ends their visit. These are worth checking first because they undermine everything else on the site if they're wrong.
Page speed matters most on mobile, where a slow-loading hero image or an oversized video background can push load time past the point most visitors will wait. An SSL certificate (the padlock icon in the address bar) is now a baseline expectation, not a bonus; browsers actively flag sites without one as 'not secure.'
Broken links do more damage than a single bad click. A visitor who hits one dead link on a site often assumes the whole site is neglected and starts second-guessing everything else on the page, including the business itself. Running a full link check across every page, not just the ones you remember creating, catches redirects that quietly stopped working after a page got renamed or removed months ago.
- SSL certificate installed and the site loads as https, not http
- Homepage loads in a few seconds on a mobile connection, not just on office WiFi
- Every internal link tested and confirmed to lead somewhere, not a dead page
- Every image compressed so it doesn't slow the page down
- Site displays correctly on at least one real phone, one tablet, and one desktop browser
- Favicon (the small browser tab icon) is set and shows the business's actual branding
SEO Checklist: Titles, Meta Descriptions, Headings, Sitemap
Search engine basics are invisible to a visitor but directly affect whether that visitor ever finds the site in the first place. Every page needs its own unique title tag and meta description, not a copy-pasted default, and each should mention the service and the city where relevant.
Heading structure matters more than it looks: one H1 per page describing what that page is about, with H2s organizing the sections beneath it, gives both search engines and visitors a clear map of the content.
It's worth checking these fundamentals live, not just in a builder's preview, since some platforms silently drop a custom title or description if a field is left blank on a specific page. A quick way to verify: view the actual page source to confirm what a search engine sees, rather than assuming what was typed into a settings panel actually made it onto the live page.
- Unique page title on every page, including the service and city where relevant
- Unique meta description on every page, written for a human, not stuffed with keywords
- One H1 per page, used correctly (not just for visual size)
- An XML sitemap exists and is submitted to Google Search Console
- robots.txt file isn't accidentally blocking search engines from the whole site
- Alt text written for every meaningful image, describing what it actually shows
Content Checklist: Core Pages, Accuracy, Legal Pages
Before launch is the last easy chance to catch content that's outdated, inaccurate, or simply missing. This is where old promotions, old team photos, and placeholder 'lorem ipsum' text that never got replaced tend to hide.
Every small business site needs a defined set of core pages at minimum, and every claim on those pages, pricing, hours, service area, should be checked against what's actually true today, not what was true when the content was first drafted.
It helps to read every page as if you were a new customer who's never heard of the business before, rather than as the owner who already knows the context. That fresh-eyes read is where most inaccurate or confusing content actually gets caught, since an owner who wrote the page months ago tends to skim past errors their own brain has learned to auto-correct.
- Home, About, Services, Contact pages all exist and are complete
- No placeholder text ('lorem ipsum,' sample copy) left anywhere on the live site
- Business hours, address, and phone number are current and correct everywhere they appear
- Every service actually offered is represented somewhere on the site
- Privacy Policy and Terms of Service pages exist, especially if the site collects any information through a form
- Spelling and grammar checked on every page, not just the homepage
Conversion Checklist: CTAs, Forms, Phone Number
A site can pass every technical and content check and still fail at its actual job if a visitor can't easily take action. This section is about removing friction between someone deciding they're interested and someone actually reaching out.
Test every form and every clickable phone number personally before launch, not just by looking at them. A phone number that displays correctly but isn't formatted as a clickable link on mobile is a quiet but real conversion killer.
Beyond the phone number and forms, check that any online booking or scheduling option actually reflects real availability, not a stale calendar left over from testing. A booking option that shows open slots which turn out to be unavailable once someone tries to confirm creates exactly the kind of bad first impression this whole checklist is meant to prevent.
- A clear call to action visible without scrolling on every page
- Phone number is a clickable tel: link that dials directly on mobile
- Contact form actually sends and someone actually receives the submission (test this live)
- A confirmation message or page appears after a form submission
- Calls to action repeated at logical points down the page, not just once at the top
Local SEO Checklist: NAP, GBP Link, Schema Markup
For any business that serves a local area, this section is as important as the core SEO checklist above it. Local search results weigh consistency and structured data heavily, and both are easy to get wrong quietly.
Schema markup (structured data that describes the business type, address, and hours in a format search engines can parse directly) isn't visible to a visitor at all, but it's one of the more reliable ways to help search engines display accurate information about the business.
It's worth double-checking that schema with a structured data testing tool rather than trusting it was added correctly the first time, since a single typo in the code can make the whole block invalid with no visible sign on the page itself. It's also worth confirming the service area listed matches what the Google Business Profile states, since a mismatch between the two undercuts the same local ranking signals both are meant to support.
- Business name, address, and phone number match exactly across the website and Google Business Profile
- LocalBusiness schema markup implemented with accurate details
- Google Business Profile is linked from the website, and the website is linked from the profile
- Service area explicitly named on the site, not just implied
Analytics and Tracking Checklist
Launching without any way to measure what happens next means the site's performance is a guess from day one. This doesn't need to be complicated, but it does need to be in place before launch, since traffic and conversions from before tracking was installed are gone for good.
Beyond basic page-view tracking, set a simple goal for what actually counts as a conversion on this specific site, a form submission, a phone click, a booking request, so the data collected from day one answers the question that actually matters: is the site bringing in business, not just visitors.
- Analytics installed and confirmed to be recording real visits (test this before launch, not after)
- Conversion tracking set up for form submissions and phone clicks, if the platform supports it
- Google Search Console connected and the sitemap submitted
Post-Launch Checklist: The First 30 Days
Launch day isn't the finish line, it's the point where real data starts coming in. The first 30 days are worth a dedicated check-in to catch anything that only shows up under real traffic: a form that worked in testing but fails for some visitors, a page that ranks for the wrong keyword, a broken link that appeared after launch.
This window is also when early technical issues that only show up under real-world conditions tend to surface: a contact form that works from one browser but not another, a page that loads slowly only on certain phone models, or a broken link that appeared because a page got moved after launch without updating every reference to it.
- Confirm the site is indexed in Google (search 'site:yourdomain.com' to check)
- Review analytics weekly for the first month, watching for pages with high traffic but no conversions
- Ask a handful of real customers to try the site on their own phone and report anything confusing
- Confirm every automated notification (form submissions, quote requests) is landing where it should
Printable Quick-Reference Checklist
Running through all 40 items above by hand, page by page, is exactly the kind of work that eats an afternoon and still gets skipped when things get busy. That's a fair reason to hand the whole list to a team that builds it in correctly from the start rather than checking it after the fact.
A checklist like this is only useful if it actually gets followed under deadline pressure, which is exactly when items tend to get skipped. Building the habit of running through it methodically, rather than trusting memory, is what separates a launch that goes smoothly from one that surfaces embarrassing gaps in the first week.
NXTDIGITAL sites are built to pass this checklist by default: security, mobile optimization, accurate local details, working forms, and clean SEO fundamentals are part of every build, not an optional add-on. If you'd rather see a finished, checklist-clean site than run through 40 items yourself, start at /kickoff and let it come out right the first time.
Last updated 2026-07-23