Technical SEO problems prevent Google from properly crawling, indexing, and understanding your website. They're often invisible to visitors but visible to search engines - which means a site can look fine to you while performing poorly in search.
Start with Google Search Console
If your funeral home website isn't connected to Google Search Console, that's the first gap to close. It's free, and it's the most direct signal Google gives you about how it sees your site. Look specifically for:
- Coverage errors - pages marked as "Excluded" or "Error" that should be indexed
- Core Web Vitals - page speed and layout stability scores, especially on mobile
- Manual actions - a penalty from Google that could be suppressing all your rankings
Compare important service, location, obituary-resource, and contact pages against their actual indexing state, and inspect pages that are excluded, redirected, canonicalized elsewhere, or blocked when they should be discoverable.
Severity: Critical when a primary service, contact, or genuine location page cannot be indexed or resolves incorrectly. Owner: Developer or technical SEO owner. Corrective action: Fix the specific blocking directive, canonical, redirect, rendering, or internal discovery problem. Validation: Re-test the live URL, inspect the rendered page, and confirm the intended canonical and indexing state in the relevant search tooling.
Mobile Usability
Many families searching for funeral services are doing so from a mobile phone under significant emotional stress. A site that's hard to navigate on a small screen isn't just a UX problem - Google uses mobile-first indexing, meaning it evaluates the mobile version of your site when deciding where to rank you. Test your site at Google's free PageSpeed Insights tool and note any mobile usability failures. Check the homepage, immediate-contact path, core services, directions, and forms, and confirm that telephone links work and forms can be completed on representative devices.
Severity: High when a family cannot reliably reach contact or service information on mobile; lower when the issue affects only nonessential visual polish. Owner: Developer with content or operations input. Corrective action: Address the specific rendering, layout, asset, script, or form problem. Validation: Re-test the same task on mobile after deployment and compare the relevant field data or lab diagnostics where available.
HTTPS and Security
Your site should load securely over HTTPS. If the browser shows a "Not Secure" warning, some visitors - and some search engines - will distrust the site. Check that your SSL certificate is active and that all pages redirect from HTTP to HTTPS without errors. Confirm too that alternate hostname versions converge on the intended URL and that canonical tags do not point important pages to unrelated destinations.
Severity: High when users encounter certificate warnings, redirect loops, or canonicals that remove important pages from consideration. Owner: Developer or hosting owner. Corrective action: Repair certificate, redirect, and canonical configuration at the template or server level. Validation: Test representative URLs from an external browser and crawl the final site to confirm consistent resolution.
Crawl Errors and Broken Links
Broken internal links waste crawl budget and confuse users. Tools like Screaming Frog (free up to 500 URLs) can scan your site and flag 404 errors and redirect chains. Even without crawl software, a manual check of your main navigation and service pages will catch obvious broken paths.
Severity: High for broken paths in primary navigation, service journeys, contact flows, or heavily linked templates; lower for isolated obsolete references. Owner: Developer or content manager, depending on the cause. Corrective action: Restore the intended page, update the link, or redirect only when there is a genuinely relevant replacement. Validation: Re-crawl the affected template and manually follow the repaired path from the pages families actually use.
Diagnostic signal: If Search Console shows fewer indexed pages than you have on your site, something is blocking Google from reading your content.