Ad units placed carelessly — in a template that only some pages use, above content that shifts as it loads, in a spot mobile visitors never reach — earn less than the same units placed with actual thought about where visitors’ attention and scroll behaviour genuinely are.
Placement affects earnings more than most people expect
Two sites with identical traffic and identical ad units can earn meaningfully different amounts based purely on where those units sit on the page — above the fold versus buried below unengaged scroll, next to content versus isolated in a sidebar nobody looks at.
AdSense code placement & ad unit implementation
Ad units placed with actual thought about scroll behaviour, not just convention or guesswork.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your AdSense account with the ad units you want implemented
- Confirmation of which pages or templates should show ads
- Any placement preferences or restrictions (for example, not within specific content types)
This or something else?
| You want ad units correctly placed and implemented for the first time | This fix covers it |
| Ad units are placed but causing layout shift | Ad-induced layout shift (CLS) correction |
| You want Auto Ads instead of manually placed units | Auto Ads configuration & density tuning, a different approach |
| ads.txt shows an error, separate from placement | AdSense ads.txt setup & error resolution |
What we do
- Review your site’s actual layout and typical visitor scroll behaviour
- Recommend placements based on genuine visibility, not just convention
- Implement the ad code correctly across the specified pages and templates
- Confirm units render correctly on both desktop and mobile
- Check for any layout shift introduced and adjust if needed
- Verify units are actually serving ads, not just present in the code
What is included
- Ad units correctly implemented in reviewed, deliberate placements
- Verified rendering across desktop and mobile
- A check for layout shift introduced by placement
- Confirmation units are actively serving
Not included
- ads.txt setup, a separate, related fix if not already done
- Ongoing optimisation as you test different placements over time
- Auto Ads configuration, a different approach to the same goal
- Guaranteeing a specific revenue outcome, which depends on factors beyond placement
Questions about this fix
Can you guarantee this will increase my ad revenue?
No, and we wouldn't promise a specific number — placement affects earnings potential, but actual revenue also depends on traffic, niche, and advertiser demand that are outside what implementation alone controls.
Will ads make my site look cluttered or unprofessional?
Not if placed thoughtfully, which is the actual point here — we aim for a balance between visibility and a site that still looks like yours, not maximum ad density.
Should I use manual placement or Auto Ads?
It depends on how much control you want — manual placement (this fix) gives you precise say over where ads sit; Auto Ads lets Google decide automatically, which is simpler but less predictable.
Will this affect my page load speed?
Ad code does add some load, which we account for in placement and implementation — if speed is a major concern, that's worth flagging so we can balance it against ad visibility.
Can I have different ad placements on mobile versus desktop?
Yes, that's often the right approach given how differently visitors scroll and view content on each, and we implement responsive placement accordingly.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.