--- title: "Diagnose technical SEO problems and get engineering to fix them without writing code" description: "A marketing manager's method for technical SEO: read audits by revenue, diagnose five common failures in Search Console, and win engineering time." canonical: "https://scalewithsearch.com/articles/marketing-managers-technical-seo-guide" date: "2026-03-20" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Diagnose technical SEO problems and get engineering to fix them without writing code. You manage a marketing team. A content strategist writes articles, a designer builds landing pages, and a paid media specialist runs ads. Then your SEO consultant delivers a 47-page technical audit about canonical errors, render-blocking resources, and orphaned pages. You forward it to engineering. The reply: "Not a priority." Organic traffic drops 30 percent. The consultant blames the JavaScript rendering issue on page 23. Engineering blames content. This guide gives you procedures to diagnose the common failures, read developer objections, rank fixes by return, and write requests that engineering schedules. None of it needs code. ## Learn the three stages Technical SEO covers three stages: - **Crawling** is how Google discovers pages. - **Rendering** is how Google runs JavaScript to see the content. - **Indexing** is how Google decides which pages to keep and rank. **A crawl problem** shows as pages that exist but do not appear in Google Search Console. You published 50 posts last month; Search Console shows 12 indexed. Common causes are broken internal links, `robots.txt` blocks, long redirect chains, and server timeouts. None needs you to code. All need coordination with whoever controls the CMS, hosting, or CDN. **A rendering problem** occurs when JavaScript builds the content and Google's crawler sees an empty page. The page loads in Chrome but shows no content in the Search Console URL Inspection tool. Your developer says the site works, and for users it does. If Googlebot cannot render the script that loads your product descriptions, those pages do not rank. The fix is often architectural: move critical content into server-rendered HTML. The guide to [how Googlebot renders JavaScript](/articles/googlebot-javascript-rendering) explains the pipeline. **An indexing problem** happens when Google crawls and renders a page but does not index it. Causes include duplicate content, thin content, canonical errors, and `noindex` tags. Search Console names the excluded pages and the reason. Your job is to decide whether each page should be indexed, then brief whoever makes the change. "Fix these 200 errors" goes nowhere, because SEO tickets compete with features, security patches, and infrastructure work. You need triage that turns SEO impact into engineering priority. ## Read an audit by revenue, not issue count Screaming Frog finds 1,847 issues. The Ahrefs site audit lists 932 warnings. Search Console shows 15 indexing errors. Ignore the counts. Use four filters. **Revenue impact.** Pull your top 100 organic landing pages from Google Analytics. Compare them with the audit. If 80 of the 100 have no technical errors, technical SEO is not your bottleneck; content or links are. If 60 of the 100 have errors, technical fixes will move results. **Owner.** Many "technical" issues need no developer: | Owner | Typical fixes | |---|---| | Content team | Missing meta descriptions, thin content, duplicate title tags | | Marketing operations | Broken internal links in posts, wrong canonical settings in CMS templates | | IT or DevOps | Server status codes, `robots.txt` rules, XML sitemap generation | | Engineering | JavaScript rendering, structured data, responsive layout | Route each issue to its owner. If the content team can fix 200 missing meta descriptions in two days, engineering never sees those tickets. **Size.** Quick wins, such as redirect fixes, `robots.txt` updates, and sitemap submissions, take hours or days. Structural projects, such as a move to server-side rendering, faceted navigation controls, or a headless CMS, take months. Do the quick wins first. They hold traffic steady while you argue for the structural work. **Ground truth.** Screaming Frog and Ahrefs simulate Googlebot. Search Console reports what Google saw. If a crawler flags 500 pages but Search Console shows them indexed with no warnings, those flags do not matter to Google. The [technical SEO audit guide](/articles/technical-seo-audit) covers the full audit scope. ## Diagnose the five common failures Most technical SEO emergencies fall into five types. You can diagnose all five without code. ### 1. Indexing collapse **Symptom.** The Search Console Page indexing report shows "Discovered - currently not indexed" or "Crawled - currently not indexed" for pages that should rank. Google renamed the Coverage report to Page indexing in 2022. **Diagnosis.** 1. Open the Page indexing report and select the reason. 2. Take a sample of 10 URLs. 3. Run each through URL Inspection. 4. Read the reason: duplicate, low quality, canonical to another URL, or not yet crawled. **Your action.** For a duplicate, set the canonical to the main version in the CMS page settings. For a thin page, merge or delete it. For a `robots.txt` block, ask IT to lift it. For a sound page that Google has not reached, select "Request indexing" in URL Inspection. IndexNow notifies Bing and other participating engines, but Google does not use it. **Escalate when** URL Inspection shows "Crawled - currently not indexed" for a unique, substantial, correctly configured page. Engineering then checks server response times and internal link structure. ### 2. JavaScript rendering failure **Symptom.** The page looks complete in Chrome. The URL Inspection screenshot shows blank or partial content. **Diagnosis.** In URL Inspection, select Test live URL, then View tested page. Compare the rendered HTML with the live page. If product descriptions, prices, or call-to-action buttons are missing, Google cannot see them either. **Your action.** Record the missing content and take screenshots of both versions. Ask your developer: "Can we move [missing content] out of client-side JavaScript into server-rendered HTML?" **Escalate** at once. No CMS setting fixes this. The fixes are server-side rendering (SSR) or static site generation (SSG). Dynamic rendering, which serves pre-rendered HTML to bots only, still works, but Google now calls it a workaround and not a long-term solution. ### 3. Redirect chains and loops **Symptom.** Search Console lists many "Page with redirect" URLs, users report slow loads, or a crawler reports chains of two or more hops. **Diagnosis.** Paste a sample URL into a redirect checker. More than one hop, such as A to B to C, is a chain. "Too many redirects" is a loop. **Your action.** Map each hop and who controls it. Chains often form when marketing adds a CMS redirect, IT adds a server redirect, and the CDN adds a third. Nobody knows all three exist. Replace the chain with one redirect from the original URL to the final one. The [redirect chains guide](/articles/redirect-chains-301-developers) shows the developer side. **Escalate when** the redirects live in `.htaccess` or server configuration you cannot reach. If they live in CMS settings, fix them yourself. ### 4. Sitemap and robots.txt errors **Symptom.** A sitemap submits thousands of URLs and many show "Submitted URL not indexed". Or a crawler reports that `robots.txt` blocks important pages. **Diagnosis.** Open the sitemap, usually at `/sitemap.xml`. Check that it lists only pages you want indexed, with no `noindex` pages, missing pages, or redirects. Then open `/robots.txt` and check whether a `Disallow` rule blocks pages you want indexed. **Your action.** Remove URLs that should not be indexed, such as `/cart`, `/checkout`, and internal search results. Many CMS plugins produce bloated sitemaps by default, so set the plugin to exclude those page types. Remove any `Disallow` rule that blocks a critical page. Google retired the robots.txt Tester in December 2023. Use the robots.txt report in Search Console and URL Inspection to check a specific URL. **Escalate when** the server generates the sitemap or `robots.txt` outside the CMS. Give engineering the exact URLs to include and exclude. ### 5. Mobile rendering gaps Google retired the Mobile Usability report and the Mobile-Friendly Test in December 2023. The underlying risk remains. Google indexes the mobile version of each page, so content that is missing or broken on mobile is missing for Google. **Symptom.** Mobile conversion or engagement falls behind desktop, or URL Inspection, which crawls as a smartphone, shows content that differs from desktop. **Diagnosis.** Open the affected pages on a phone. Check that text is readable without zoom, buttons are easy to tap, and nothing extends past the screen. Run Lighthouse in Chrome DevTools with mobile emulation for a second view. **Your action.** Send screenshots and page examples to your designer or developer. Most issues come from fixed-width containers or CSS that is not responsive. On WordPress, Shopify, or Webflow, a failure usually means custom code overrode the theme. **Escalate** at once when mobile carries most of your traffic. Three issues never wait for triage: - a manual action in Search Console; - a security issue, such as malware or hacked content; - mobile failures on a site where most traffic is mobile. ## Translate developer objections An SEO fix pays off slowly, and its attribution is unclear, so it loses to features with a visible user benefit. Translate each objection, then answer the real concern. The [engineering buy-in guide](/articles/engineering-buy-in-seo) goes further. **"This will take weeks to build."** The proposed fix is larger than the problem needs. Ask your consultant for a minimum viable fix. If server-side rendering takes eight weeks, what two-week change captures most of the value? Often it is static HTML for the critical content on the top landing pages only. **"We have no data that this will increase traffic."** The objection asks for a forecast. Compare pages that have the issue with pages that do not. Suppose pages without heavy JavaScript rank in positions 1 to 3, and similar JavaScript-heavy pages rank 8 to 12. Show that gap. Estimate the lift with the average CTR for those positions. **"This conflicts with our architecture."** The recommendation assumes a stack you do not run. Put the developer and the consultant on one call. The developer explains the architecture. The consultant proposes fixes that fit it. Advice written for WordPress does not fit a React single-page app on Vercel. **"Can't marketing fix this in the CMS?"** The objection assumes the issue is content. Use URL Inspection to show that the rendered HTML differs from what the CMS editor shows. If the developer still names a CMS setting, ask which one. If they cannot name it, the issue is code. **"SEO is not on this sprint's roadmap."** SEO has not been expressed as a product priority. Pull organic revenue for the affected pages from GA4. State the lift you expect and the assumption behind it. Convert it to monthly revenue with your average organic session value. Give that number to the product manager who owns the roadmap. Developers are usually right about implementation limits, such as "our hosting cannot run SSR". They can be wrong about SEO priority, such as "alt text does not matter". Check such claims against Google Search Central documentation or r/TechSEO, and ask for a source. If none comes, get an outside second opinion. ## Build a loop between SEO and engineering One-off fixes do not scale. Put SEO checks into the development process so issues stop before production. ### Pre-launch checklist Every new page, section, or feature passes this list before release: - The page has a unique, descriptive title tag and meta description. - The URL is short, descriptive, and follows the existing structure. - At least one relevant existing page links to it. - It shows an LCP of 2.5 seconds or less on mobile in PageSpeed Insights. - It renders correctly in URL Inspection. - It appears in the XML sitemap. - It carries structured data where a type applies, such as Product or Article. Make the list a required step before "Done" in Jira, Asana, or Monday. A product manager or QA tester can check most items. ### Monthly SEO and development sync Hold 30 minutes a month with a standing agenda: 1. Page indexing report: any new errors? 2. Core Web Vitals trend: any regression in Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), or Interaction to Next Paint (INP)? INP replaced First Input Delay (FID) in March 2024. 3. Upcoming launches that touch URLs, navigation, or templates. 4. SEO tickets ready for the next sprint. ### Staging tests Test every SEO change in a staging environment that mirrors production. Your consultant crawls staging and validates the fix before release, so a conflict such as broken mobile layout never reaches users. ### Pattern documents After you solve an issue once, write it down so developers can reuse it. Example: ```text Pattern: add Article structured data to blog posts When to use: every blog post template Implementation: 1. Add a script element of type application/ld+json to the page head. 2. Follow the schema.org Article structure and Google's Article documentation. 3. Validate with the Rich Results Test. CMS integration: name the plugin and the settings here. ``` Engineering then applies the pattern without a meeting. Avoid FAQ markup in new patterns. Since August 2023, Google shows FAQ rich results only for well-known, authoritative government and health sites. ## Rank technical debt by return Alt text on 1,000 archive images with no traffic is wasted effort. One redirect chain on the homepage is high leverage. Plot each issue by traffic impact and effort: | | Low effort | High effort | |---|---|---| | **High impact** | Do now | Plan for next sprint | | **Low impact** | Batch into maintenance sprints | Do not do | High impact and low effort are quick wins: redirect fixes, `robots.txt` updates, and sitemap corrections. Ship them within days. High impact and high effort are strategic projects: rendering overhauls, mobile rebuilds, and international SEO. Forecast the return, write a business case, get executive approval, and schedule a quarter. Low impact and low effort go to the maintenance backlog, such as alt text on low-traffic pages or minor HTML validation errors. Low impact and high effort do not get done. Suppose a fix needs two weeks of developer time for pages with 100 sessions a month. Redirect those pages to better ones and remove them. The [SEO technical debt backlog guide](/articles/seo-technical-debt-backlog) shows how to run this list over time. Estimate the traffic opportunity for each issue: ```text Traffic opportunity = affected URLs × average monthly sessions per URL × expected lift ``` Example: 200 product pages have a rendering problem. Each averages 500 organic sessions a month. Assume a conservative 15 percent lift and state that assumption: ```text 200 × 500 × 0.15 = 15,000 additional sessions per month ``` Multiply by your average organic session value from GA4 to get monthly revenue. Use the same method for the cost of inaction. Suppose organic sessions fell from 100,000 to 80,000 a month while paid and social grew. Multiply the 20,000 lost sessions by the session value. Take that number to your CMO or VP of Engineering. ## Decide who does the work You can start without a consultant. Google Search Console and PageSpeed Insights are free, and the free tiers of Ahrefs Webmaster Tools and Semrush Site Audit catch most common issues. Search Console links each error type to documentation. Expect about three months before you diagnose with confidence. Review technical SEO monthly for sites with more than 100,000 organic sessions a month and quarterly for smaller ones. Turn on Search Console email alerts so new indexing errors and Core Web Vitals regressions reach you between reviews. For a WordPress or Shopify site under 10,000 pages, a freelancer is usually enough. For a site over 100,000 pages, a custom stack, or several international domains, hire an agency with technical specialists. An agency has seen more edge cases. Expect an agency retainer to cost a multiple of a freelancer's monthly bill for this work. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```