SEO
eTilbudsavis
Technical SEO across borders
SEO analysis and technical optimisation focused on indexing, landing pages and visibility in Google.
Visit etilbudsavis.dk
Technical SEO
Technical SEO where the issues get found and fixed
Technical SEO decides whether Google can crawl, understand and index your pages at all. With 16 years of developer experience I find the issues and fix them in the code myself. You get a review of the whole site and fixes you can read off in Search Console.
- I usually reply the same day
- Written estimate before work starts
Technical SEO
Typical technical SEO tasks
- A crawl of the whole site to see what Googlebot actually meets, rather than a single page test.
- A rendering check: does the content exist in the HTML, or only after JavaScript has run?
- Canonicals, including chains where a page points to a page that itself points somewhere else.
- Hreflang on multilingual sites, verified in both directions.
- Status codes: 404 pages answering 200, redirect chains and redirects to the front page.
- Sitemap and robots.txt, which surprisingly often contradict each other.
JavaScript and rendering
Google can run JavaScript, but it happens in a later pass than the first crawl, and nobody knows when. On sites with many pages that becomes a concrete problem, because a share of the pages never get rendered.
I check whether the content that needs to rank sits in the initial HTML. If it does not, we look at whether it can be rendered on the server instead and how big a change that would be in your setup.
Large sites and crawl budget
On sites with hundreds of thousands of URLs, crawl budget becomes a real constraint. The work consists of closing off what should not be crawled, such as filter parameters, sort orders and internal search results, so the capacity goes to the pages that earn money.
Here server logs are worth more than any analysis tool, because they show in black and white what Googlebot spends its time on.
What you get
Concrete deliverables, not a report of recommendations someone else has to find time for.
- A crawl review
The whole site run through a real crawler, with the technical findings prioritised by how much visibility they cost you.
- A rendering check
An answer to whether your content exists in the initial HTML, or whether Google has to wait for JavaScript to see it.
- Fixes in the code
Canonicals, hreflang, redirects and status codes put right by me, not described in a document for your developers.
- Log file analysis on large sites
Documentation of what Googlebot really spends its crawl budget on, instead of an educated guess.
The work in practice
View all casesHow it works
Four steps. You know what happens when, and you can stop after any of them.
- 01
Crawl and data review
I crawl the entire site and go through Search Console for indexing errors, coverage and search terms. That gives a picture of how far from your potential you are before anyone touches anything.
- 02
Prioritised by impact
The findings go into a list sorted by what moves the most for the least work. Each item comes with its reasoning, so you can challenge the priorities if you disagree.
- 03
Implementation in the code
The fixes are written and shipped by me: redirects, canonical tags, structured data, speed. If you have your own dev team, I deliver precise, testable tickets for them instead.
- 04
Measuring the effect over time
Rankings and organic traffic are tracked in the weeks that follow, and you get a short status every month. If a number goes the wrong way, I dig into why instead of dressing up the graph.
Brands I've worked with
Frequently asked questions
- What does technical SEO cost?
- The price is driven mainly by the number of URLs, how many systems and language versions are involved, and whether the fixes are part of the job. Send me a link to the site, I will ask a couple of questions and give you a concrete quote. You will hear from me the same day.
- What is the difference between technical SEO and regular SEO?
- Technical SEO is about whether Google can find, fetch and index your pages, while general SEO also covers content, keywords and links. The technical side is the foundation. If it is broken, the rest does not work no matter how good the content is.
- Do you take on technical SEO tasks nationwide?
- Yes. The work happens in crawlers, log files and code, so I help companies in Copenhagen, Aarhus, Odense, Aalborg and everywhere in between without leaving Herlev. Meetings happen on video, or in person in the Copenhagen area.
- How quickly can you see results from SEO?
- Technical fixes are the fastest part of SEO, but even here you should count in weeks and months rather than days. Google has to recrawl the pages before the changes count, and the bigger movements in traffic typically arrive over three to six months.
- Do you also fix the issues yourself?
- Yes, that is the whole point of my profile. I am a developer and make the fixes directly in your code or CMS, usually cheaper than handing over to another team because I am already familiar with the details. If you would rather do it yourselves, I write up the findings so your people can execute them.
- Can you do a technical audit without access to our code?
- Yes, a crawl only requires the site to be publicly accessible. Access to Search Console, and ideally server logs, lifts the audit considerably, and code access only becomes necessary if I am also implementing the fixes.
- We just launched a new site. Is technical SEO relevant already?
- Right after launch is actually one of the best moments. That is when redirects, canonicals and the sitemap typically sit half finished, and catching it now is far cheaper than discovering it as a traffic drop in six months.
- Can you monitor the technical side continuously?
- Yes, and I recommend it for sites that deploy often. A scheduled crawl that raises a flag when something changes catches an accidental noindex long before it shows in the traffic.