SEO
eTilbudsavis
Technical SEO across borders
SEO analysis and technical optimisation focused on indexing, landing pages and visibility in Google.
Read about my work for eTilbudsavisVisit etilbudsavis.dkTechnical 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.

star reviews
Read every reviewGoogle 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.
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.
Technical SEO is the part of search engine optimisation concerned with whether a search engine can find, fetch, understand and store your pages. It is the foundation under all other SEO work. If Google cannot crawl a page properly, neither good content nor strong links will help it rank.
In practice I work with four layers. Can the crawler find the page, meaning are there links to it, is it in the sitemap, and is it not blocked? Can it fetch it, meaning does the server answer quickly and with the right status code? Can it understand it, meaning does the content sit in the HTML with a sensible heading structure and correct structured data? And should it store it, or does a canonical or noindex say otherwise?
The need for technical SEO is greatest on sites with many pages, on JavaScript-heavy builds and after relaunches, where redirects and canonicals often sit half finished. But even small sites usually carry a couple of technical faults that cost visibility without being visible in a browser.
The field demands a different skill set than content work, and this is where my developer background makes the biggest difference. Where many consultants have to stop at the recommendation, I continue into the code and fix the faults, whether the site runs WordPress, Shopify, Next.js or something home-built.
Every time Googlebot requests a URL, the server answers with a status code, and that decides what Google does with the page. 200 means the page exists. 301 means it has moved permanently and that the signals should follow to the new address, while 302 is a temporary move. 404 and 410 say the page is gone, and 5xx errors mean the server has problems. If they persist, Google slows its crawling and can eventually drop the pages from the index.
The faults I find most often are soft 404s and chains. A soft 404 is a page that tells the visitor it does not exist but answers 200 to Google, so it uses up the crawler's time and can end up in the index. A chain is a redirect pointing to another redirect, typically after two or three relaunches. Every hop slows the crawler, and internal links should always point straight to the final address.
Canonical tags solve a different problem: the same content at several URLs, for example with and without parameters. A canonical tag tells Google which version should rank, but it is a hint, not an order. If other signals point elsewhere, such as internal links, the sitemap or redirects, Google chooses for itself. You can see that in Search Console, where the page is listed as a duplicate for which Google chose a different canonical.
Do not mix up canonical, noindex and robots.txt either. Robots.txt prevents crawling but not indexing, so a blocked URL can still show up in Google without a description. Noindex removes the page from the index but only works if Google is allowed to crawl the page and see the tag. Canonical gathers the signals on one version. They are three different tools, and they work against each other if used on the same page.
Structured data is a machine-readable description of what a page contains: that it is a product with a price, an article with an author and a date, or a business with an address and opening hours. The vocabulary comes from schema.org, which is why it is also called schema markup. Google recommends the JSON-LD format, where the markup sits together in a script block in the page's code instead of being woven into the HTML.
The types that most often make sense are Organization or LocalBusiness on the front page, BreadcrumbList on subpages, Article on articles and Product on product pages. Set up correctly, they can earn rich results showing, for example, price, stock status or a breadcrumb trail, but there is no guarantee. Over the years Google has cut back on which types it displays, so mark up what fits the page rather than chasing stars and extra lines in the search result.
The rule broken most often is that the markup has to match what the page says. A price in the JSON-LD that does not match the price on the page, or reviews the visitor cannot see, go against Google's guidelines. So validate every page type in Google's Rich Results Test, and keep an eye on the structured data reports in Search Console, which show errors and warnings across the whole site.
A technical SEO audit is a review of everything that decides whether Google can find, fetch and index the site's pages. It differs from a general SEO audit by going deep on the technical side and leaving content and keywords aside until the foundation has been examined. With me it consists of a crawl, a review of Search Console, a rendering check and, on large sites, an analysis of server logs.
The crawl should run as Googlebot on mobile, because Google indexes the mobile version. The result is compared with the XML sitemap and with page indexing in Search Console. That produces three lists that are almost always interesting: pages in the sitemap the crawler cannot reach through links, pages the crawler finds that are missing from the sitemap, and pages in the index that should never have been there.
The rendering check shows whether the content sits in the HTML the server sends or only arrives once JavaScript has run. The URL Inspection tool in Search Console shows how Google itself rendered a page, and it is the most reliable source. Finally the findings are prioritised by how many pages they affect and how much traffic those pages can bring, so you know what to fix first.
Technical SEO is, if anything, a discipline that can be delivered at a distance, because all the work happens in crawlers, log files, Search Console and your codebase. I sit in Glostrup near Copenhagen and solve tasks for companies in Copenhagen, Aarhus, Odense and Aalborg plus several smaller towns and a few clients abroad.
Typical enquiries are a webshop in Jutland whose pages sit as discovered but not indexed, a SaaS company in Copenhagen with a JavaScript-heavy app that Google cannot read, or a site on Funen that lost traffic after a relaunch. What they share is that the problem must be solved in the technology, not in the copy.
The collaboration runs over video and written updates, with access to your systems by agreement. If you are in the Copenhagen area, I am happy to come out for a meeting when the project starts or when something needs deciding.
Being a freelancer means a short path from finding to fixing. There is no backlog at an external development team and no account manager translating between consultant and programmer, because those two are the same person. You can always call me directly on +45 22 51 31 79.
Google can execute JavaScript, and that is often used as an argument for not worrying about it. The problem is that rendering happens in a later pass than the first crawl, and there is no guarantee of when that pass arrives.
On a small site with sixty pages it rarely matters. On a site with thirty thousand pages it means a share of them never get rendered, and those pages effectively do not exist in the index. The symptom is clear in Search Console, where pages hang as discovered but not indexed for months.
The test is simple: fetch the page without JavaScript and see whether the content that needs to rank is there. If it is not, the question is whether rendering can happen on the server instead, and what the change would require. On a Next.js or Nuxt site it is often manageable, while a pure single page app is a bigger project. Because I develop in those frameworks myself, I can both assess the scope and carry out the change.
Concrete deliverables, not a report of recommendations someone else has to find time for.
The whole site run through a real crawler, with the technical findings prioritised by how much visibility they cost you.
An answer to whether your content exists in the initial HTML, or whether Google has to wait for JavaScript to see it.
Canonicals, hreflang, redirects and status codes put right by me, not described in a document for your developers.
Documentation of what Googlebot really spends its crawl budget on, instead of an educated guess.
SEO
Technical SEO across borders
SEO analysis and technical optimisation focused on indexing, landing pages and visibility in Google.
Read about my work for eTilbudsavisVisit etilbudsavis.dkFour steps. You know what happens when, and you can stop after any of them.
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.
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.
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.
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.
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.
SEO is about ranking in the search results. GEO (generative engine optimisation) is about being cited when AI services such as ChatGPT and Google's AI Overviews answer a question. Both build on the same foundation: pages that can be crawled, understood and trusted. A page the crawlers cannot fetch and read is neither shown nor cited, so technical SEO is the base for both.
Start with Google Search Console. It is free and the only source showing what Google itself has indexed and which errors it has run into. Add a crawler such as Screaming Frog, which walks the site the way a search engine does, and PageSpeed Insights for speed. Paid tools such as Ahrefs and Semrush are good for keywords and links, but they rarely find technical errors the first two have not already shown.
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.
Structured data is code that describes the page's content in a fixed format search engines can read, for example that the page is about a product with a certain price and stock status. It uses the schema.org vocabulary and is typically written as JSON-LD. Correct structured data can earn rich results, but only if the markup matches what the page says.
A canonical tag is a line in the page's code that tells Google which URL is the preferred version when the same content exists in several places. It is typically used for pages with parameters, sorting or tracking codes in the address. Google treats it as a strong hint, not an order, so internal links and the sitemap should point to the same version.
An XML sitemap is a file listing the URLs on the site you want indexed. It helps Google discover new and changed pages, especially on large sites, but it does not guarantee indexing. Most CMSs generate it automatically, so the task is mainly to make sure it only contains pages that actually belong in the index.
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 Glostrup. Meetings happen on video, or in person in the Copenhagen area.
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.
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.
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.
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.
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.
Send your website URL, what you need solved and your desired deadline. I will assess the next step and describe what the quote includes. Larger investigations are agreed separately before work begins.
Describe your taskYour next step
Tell me about your project. I’ll get back to you with questions, options and a concrete next step.