A crawl of summitridgedental.com discovered 147 URLs across the domain. Of those, 23 return non-200 status codes, 11 are caught in redirect chains of 3+ hops, and 4 priority pages are missing from the XML sitemap entirely. The homepage canonical tag points to an HTTP URL rather than HTTPS, sending a conflicting signal to search engines about which version is authoritative. The robots.txt file blocks Googlebot from crawling CSS and JavaScript resources required for rendering, which means Google's index may contain incomplete or broken representations of key pages.
Status code breakdown across all 147 discovered URLs.
| Status | Count | Notes |
|---|---|---|
| 200 OK | 112 | Healthy indexable pages |
| 301 Redirect | 18 | 11 in chains of 3+ hops |
| 302 Redirect | 5 | Temporary — should likely be 301 |
| 404 Not Found | 9 | Broken links from internal pages |
| 500 Server Error | 3 | Intermittent on /wp-cron.php paths |
The <link rel="canonical" href="http://summitridgedental.com/"> tag on the homepage references the HTTP URL. The site redirects HTTP to HTTPS, but the canonical tag still declares the non-secure version as authoritative.
Google uses the canonical tag as a strong signal for which URL to index. A canonical pointing to HTTP contradicts the HTTPS redirect, causing index confusion. Search equity from backlinks may be split between the HTTP and HTTPS versions rather than consolidated on the HTTPS URL. This directly undermines ranking authority on the single most important page on the site.
The WordPress Settings > General configuration likely has the WordPress Address and Site Address set to http:// rather than https://. This propagates the HTTP canonical across all pages generated by WordPress.
Update WordPress Address (URL) and Site Address (URL) in Settings > General to https://summitridgedental.com. Verify that all canonical tags across the site update to HTTPS. Run a crawl to confirm no HTTP canonicals remain.
Low — 5 minutes in WordPress admin, followed by a verification crawl.
Eleven internal URL paths resolve through 3 to 5 redirect hops before reaching the final destination. Example: /dental-services → /dental-services/ → /services/dental/ → /services/ (4 hops). Each redirect adds latency and each 302 in the chain fails to pass full link equity.
Long redirect chains waste crawl budget — Googlebot may abandon chains beyond 5 hops and not index the destination page. Each hop adds 100–300ms of latency for users who click the original URL. Mixed 301/302 chains (present in 4 of the 11 cases) mean link equity is not fully transferred to the destination page.
Multiple rounds of URL restructuring (likely during theme changes or permalink updates) created layered redirects without consolidating old chains. The .htaccess file contains 34 redirect rules with several redirecting to URLs that are themselves redirected.
Audit all 34 .htaccess redirect rules and collapse every chain to a single 301 from the original URL to the final destination. Remove intermediate redirect targets. Update any internal links that point to redirected URLs to point directly to the final destination.
Medium — 2–3 hours to audit and rewrite all redirect rules.
The robots.txt file contains Disallow: /wp-content/plugins/ and Disallow: /wp-includes/ rules that block Googlebot from accessing CSS and JavaScript files required to render the page correctly.
Google renders pages using a headless browser. If critical CSS and JavaScript are blocked, the rendered page in Google's index may appear broken, unstyled, or missing interactive elements. This can cause Google to misinterpret page content, demote pages in rankings, or flag mobile usability issues that do not actually exist on the rendered site.
The robots.txt rules were likely added to prevent indexation of plugin/admin files but are overly broad — blocking entire directories that contain front-end assets, not just admin files.
Remove the blanket Disallow rules for /wp-content/plugins/ and /wp-includes/. Instead, block only specific admin-facing paths: Disallow: /wp-admin/ (except allow /wp-admin/admin-ajax.php for themes that use AJAX). Test rendering using Google Search Console's URL Inspection tool to confirm Google can fully render priority pages.
Low — 30 minutes to rewrite robots.txt and validate in Search Console.
The /book-appointment/, /insurance/, /new-patients/, and /testimonials/ pages are not listed in the XML sitemap despite being indexable, internally linked, and commercially important.
While Google will likely discover these pages through internal links, their absence from the sitemap means Google has no explicit signal that the site owner considers them important. Sitemap inclusion also provides lastmod data that helps Google prioritize recrawling after content updates.
The sitemap appears to be generated by a WordPress SEO plugin that excludes certain page templates or custom post types from the sitemap by default.
Review the sitemap generation settings in the SEO plugin (likely Yoast or RankMath). Ensure all public, indexable page types are included. Verify the four missing pages appear in the updated sitemap and submit via Search Console.
Low — 15 minutes in plugin settings.
Seven pages were discovered only through the XML sitemap — no internal links on any other page point to them. These include /insurance/, /new-patients/, /testimonials/, and 4 archived blog posts.
Orphan pages receive no internal link equity and rely entirely on the sitemap for discoverability. Google treats pages with no internal links as low-priority, making them less likely to be crawled frequently or ranked competitively. Users cannot navigate to these pages through the site's own link structure.
These pages were either created without being linked from navigation/content, or the links that once pointed to them were removed during a redesign or content update.
Add internal links to all 7 orphaned pages from relevant contextual locations. /insurance/ and /new-patients/ should be linked from the main navigation or footer. /testimonials/ should be linked from service pages. Blog posts should be linked from related content or a blog archive page.
Low — 1 hour to add contextual internal links across the site.
Five URLs return 302 (temporary) redirects to their final destinations. Based on the URL patterns (old service page slugs redirecting to new service page slugs), these redirects are clearly permanent restructuring, not temporary content moves.
302 redirects do not pass full link equity to the destination URL. Any backlinks or internal link authority pointing to the original URL is partially lost rather than being transferred to the new URL. Over time, this accumulates into measurable ranking authority loss on the destination pages.
The redirects were likely created using a WordPress redirect plugin that defaults to 302 rather than 301, or the .htaccess rules explicitly specify 302 without understanding the SEO implication.
Change all 5 redirects from 302 to 301 in the redirect plugin or .htaccess. Verify each redirect resolves correctly after the change.
Low — 15 minutes.
Ranked by likely traffic and visibility impact. Working top-to-bottom recovers the most search visibility first.
| # | Action | Priority | Effort |
|---|---|---|---|
| 1 | Fix homepage canonical to HTTPS Consolidates all link equity on the correct HTTPS URL for the most important page. |
Critical | 5 min |
| 2 | Unblock CSS/JS resources in robots.txt Allows Google to fully render all pages, preventing index quality degradation. |
High | 30 min |
| 3 | Collapse all redirect chains to single 301 hops Recovers crawl budget, eliminates redirect latency, and transfers full link equity. |
High | 2–3 hrs |
| 4 | Add missing priority pages to XML sitemap Ensures Google recognizes all commercially important pages. |
Medium | 15 min |
| 5 | Add internal links to 7 orphan pages Restores link equity flow and user navigability to isolated pages. |
Medium | 1 hr |
| 6 | Convert 5 temporary 302 redirects to permanent 301s Ensures link equity passes through redirects intended to be permanent. |
Low | 15 min |
Full domain crawl of summitridgedental.com covering 147 discovered URLs. Crawl included response codes, canonical tags, meta robots directives, robots.txt analysis, XML sitemap validation, internal link structure, and crawl depth mapping. No Google Search Console access was provided.
Backlink profile analysis, keyword ranking positions, and off-page SEO signals are outside scope. Content quality and metadata editorial optimization are covered by the Content & Metadata Quality Review (#4). Structured data and rich result eligibility are covered by the Structured Data & Rich Results Readiness (#8).
Crawl data represents the site state at the time of review. Sites that publish content frequently or change URL structures may see different results on a subsequent crawl. Crawl was limited to 500 URLs; larger sites may have additional issues beyond the crawl boundary.
The Content & Metadata Quality Review (#4) is the natural companion — it uses the same crawl infrastructure to assess editorial quality (broken links, title/meta description hygiene, heading structure, thin content). Together, #3 and #4 provide a complete picture of technical SEO health and content quality. Both are included in the Performance Tune-Up package (#11) alongside performance and security reviews.