The honest answer
We made all 14 of these mistakes on the Striveloom website. We are not writing this post from the outside looking in. We ran our own audit in late 2025, found the same problems we now find on client sites, and spent 60 days correcting them in priority order. Organic search impressions went from 340 per month to 4,200. Clicks went from 12 to 196. That data is from our own Search Console dashboard, not from a case study we polished.
Most of these mistakes are common because they are invisible until you look for them. No one tells you that your structured data has validation errors. No one tells you that a robots.txt disallow line is blocking Google from your blog. The site looks fine in a browser. The SEO problems live in layers that only appear when you run the right tools.
Here are all 14, ranked roughly by how much impact fixing them had.
The Technical Mistakes (Numbers 1-7)
Mistake 1: No structured data anywhere
We had zero schema markup when we first audited the site. No Organization schema, no Service schema, no FAQPage schema. This meant no rich results eligibility, no entity recognition in Google's Knowledge Graph, and no AI Overview citation potential (which increasingly requires structured, well-labeled content).
Fix: Implement Organization schema on every page via the site-wide layout. Add Service schema to each service page. Add FAQPage schema to FAQ sections. Validate every type with Google's Rich Results Test before deploying. Total implementation time for a developer who knows the task: one day.
Mistake 2: LCP above 4 seconds on mobile
Our hero section loaded a 1.8MB PNG with no compression, no WebP conversion, and no CDN. On mobile, our Largest Contentful Paint was 4.3 seconds. The 'Good' threshold is 2.5 seconds (per web.dev, 2024). Everything above that is a signal to Google that the page delivers a poor experience.
Fix: Convert all above-the-fold images to WebP. Use Next.js Image component (or equivalent) for automatic format selection and lazy loading below the fold. Add a CDN layer if not already present. Our LCP dropped to 1.7 seconds after these changes alone.
Mistake 3: CLS from layout shifts on load
Our navigation menu and a promotional banner both appeared after the initial paint, pushing content down and creating a Cumulative Layout Shift score of 0.22. The 'Good' threshold is under 0.1.
Fix: Reserve space for all dynamically loaded elements using explicit width and height attributes on images and fixed dimensions on banner containers. This is a CSS discipline problem more than an infrastructure problem.
Mistake 4: Broken canonical tags
Two of our service pages had canonical tags pointing to a staging domain URL that no longer existed. This told Google that the canonical version of our content was on a site that returned a 404 error. We had no idea. Screaming Frog caught it in the first crawl.
Fix: Crawl your site monthly with Screaming Frog or a similar tool and filter for canonical tag values. Any canonical pointing offsite or to a non-200 URL is a problem. Fix the canonical to point to the correct live URL.
Mistake 5: Missing XML sitemap in Search Console
We had a sitemap.xml file. We had never submitted it to Search Console. Google was finding our pages through crawling, but not through the declared sitemap. This meant our sitemap-driven freshness signals were not being used.
Fix: Go to Search Console, navigate to Sitemaps, and submit the full URL of your sitemap file. If you are on Next.js, the App Router generates a sitemap automatically from a sitemap.ts file. Submit it once and let Search Console track discovery.
Mistake 6: Missing meta descriptions on 60% of pages
We had meta descriptions on the homepage and three blog posts. Every other page was getting auto-generated snippets from Google, which usually meant our first paragraph rather than a crafted pitch. Google truncates at around 160 characters, so anything over that gets cut.
Fix: Write a unique meta description for every indexable page. Keep it between 130 and 160 characters. Frame it as a direct answer or a specific benefit, not a generic brand statement. This does not directly affect rankings, but it affects click-through rate, which affects traffic, which affects behavioral signals Google uses.
Mistake 7: Images with no alt text
We had 47 images on the site with empty or missing alt attributes. This matters for two reasons: accessibility (screen readers cannot describe the image) and SEO (Google cannot understand what the image depicts without text context).
Fix: Add descriptive alt text to every meaningful image. "Hero image" is not descriptive. "Next.js development agency team working on a client dashboard" is descriptive. For decorative images, use an empty alt attribute (alt="") so screen readers skip them.
The Content Mistakes (Numbers 8-11)
Mistake 8: Blog posts under 500 words
Our original blog had 11 posts. Eight were under 500 words. These posts were not earning any search visibility because they had no depth to offer. Google's Helpful Content guidance is explicit: it values content with first-hand expertise and sufficient depth to fully address the reader's question.
Fix: Write fewer posts at greater depth. Our current standard is a minimum of 1500 words per post, with a source citation, a data table, and a clear answer-first structure. We unpublished the 8 thin posts and rewrote 3 of them at full length.
Mistake 9: No topic cluster structure
Our blog had 11 posts on 11 completely different topics. No thematic clustering, no internal links between related posts, no pillar pages. From Google's perspective, the site had no topical authority in any subject area. It looked like a random collection of content.
Fix: Build a topic cluster map. Pick 3 to 5 core topics your agency wants to rank for. Write a pillar post for each topic (2000-plus words, comprehensive). Write 4 to 8 spoke posts on related subtopics. Link spokes to the pillar and link the pillar to each spoke. Repeat.
| Cluster Type | Word Count Target | Internal Links | Update Frequency |
|---|---|---|---|
| Pillar page | 2000-3000 words | Links to all spokes | Every 6 months |
| Spoke post | 1200-1800 words | Links back to pillar | Every 12 months |
| FAQ post | 800-1200 words | Links to pillar + 1 spoke | As needed |
| Case study | 1000-1500 words | Links to relevant service page | No update needed |
Mistake 10: No internal links from the homepage to service pages
Our homepage linked to About, Contact, and Blog. It did not link to any of our service pages with keyword-rich anchor text. This meant the page with the most inbound link authority on our domain was not distributing that authority to the pages we needed to rank.
Fix: Add at least 5 descriptive internal links from the homepage to key service pages. Use anchor text that reflects the keyword you want each service page to rank for. Not "click here." Not "learn more." "Next.js web development services" or "AI-powered marketing automation."
Mistake 11: Service pages with no keyword research behind them
We had service pages with titles like "What We Do" and "Our Services." These titles had no keyword targeting behind them. No one is searching "what we do digital agency."
Fix: Run keyword research for each service you offer. Find the phrase that people actually type when looking for that service. Build service pages around those phrases in the title, URL, H1, and first paragraph.
The Trust and Authority Mistakes (Numbers 12-14)
Mistake 12: No external citations in content
Every claim we made in our blog posts was unsourced. Google's E-E-A-T framework rewards content that demonstrates expertise through external sourcing, among other signals. Our posts read like opinion with no research backing.
Fix: For every factual claim in a post, trace it to a named source (a study, a platform's official data, a credible publisher). Cite the source inline and list it in a sources section. This is standard practice in quality editorial content.
Mistake 13: No author information on posts
Our blog posts had no author byline, no bio, and no author-level E-E-A-T signals. From Google's perspective, the content had no human behind it.
Fix: Add an author schema to every post. Include a real name, a job title, a brief bio, and a link to a profile or LinkedIn. This is a lightweight change with meaningful trust implications.
Mistake 14: Never checking Search Console for errors
We were not monitoring Search Console at any regular interval. We had manual action flags that had been sitting unaddressed. We had crawl errors on pages that we thought were indexed. We had no idea because we were not looking.
Fix: Block 20 minutes every Monday to review Search Console. Check the Coverage report for new errors. Check the Core Web Vitals report for regressions. Check the Performance report for ranking changes on your key pages. Set email alerts for manual actions and security issues.
What this means in practice
Running through this list ourselves took two dedicated weeks. The fixes took another six weeks to implement in priority order. We started with the free and fast (Search Console, canonical tags, meta descriptions, alt text), then moved to structured data, then content depth, then Core Web Vitals.
The results were not instant, but they were real. Organic impressions from 340 to 4,200 within 90 days. We cannot attribute every impression to every fix because we were making multiple changes simultaneously. But the timing correlation is hard to argue with.
If you want help running the same audit on your agency site, our SEO and technical audit service uses the exact checklist above. We deliver a prioritized fix list within five business days and can execute the technical fixes or hand them off to your team.
The mistakes are not unusual. The willingness to audit your own site without ego is.
