Where I start the cooperation
The start of the cooperation is not the sale of a package, but establishing what the company really needs and what stage its website is at. I am interested in which services are to be promoted, which locations matter most, where enquiries come from today and whether the site is to support only local client acquisition or also build broader topical visibility. I also check who on the company’s side is responsible for implementation, content, access to the website and communication, because the realistic pace of work and a sensible scope for the first changes depend on it.
From a freelancer’s perspective, setting the cooperation up well right from the start matters to me. Instead of promising everything at once, I separate the critical elements from those that can wait. Sometimes the offer and the site structure need to be put in order first, and only then is it time to think about expanding the content or off-site work. Such a start saves time and budget, because it does not scatter attention across tasks that look good in a report but do not solve the main business problem.
How I collect the input data
Good local SEO starts with data, but not only the numerical kind. Besides information on current visibility, I need to understand the offer itself: what the company calls its services, how the variants differ, which of them matter most for sales and which questions come up most often before contact. If data is available from analytics, the site’s history or the panels related to search traffic, I use it as support. Equally important, however, are sales materials, the pricing logic of the offer, information about the area served and the advantages that can honestly be shown in the content.
At this stage I also collect the information that is often overlooked and later blocks effective implementation. The point is whether the website has up-to-date service pages, whether the contact details are consistent, whether there is a clear division into locations, and whether the company publishes content that can be expanded towards users’ questions. This is also a good moment to establish which content can support visibility in the classic search results and at the same time be readable for systems that generate answers on the basis of well-organised information.
Audit of current visibility
For me, a visibility audit does not mean producing a long list of technical comments without context. First I check whether the site has a problem with indexing, duplication, keyword cannibalisation between pages, faulty internal linking or services that are described too weakly. I also look at whether the site architecture makes it harder for the search engine to understand which pages are key and which queries they are meant to serve. In many local projects the main obstacle is not one big error but the sum of small oversights: imprecise headings, content that is too general, a badly laid out menu and a lack of order in the URLs.
The second part of the audit concerns the quality of the local signals and the overall trust in the brand in the search engine. I check whether the company communicates consistent details, whether the service pages match what can be seen elsewhere on the web, and whether the local profile and the website support each other instead of contradicting each other. I also pay attention to whether the site shows experience, accountability and specifics, because this affects not only how the user perceives it, but also whether the content has a chance of being treated as a credible source in the organic results and in the answers generated by AI systems.
Local keyword analysis
Local keyword analysis does not end with a list of keywords containing the name of the city. I divide the queries by intent: transactional, comparative, informational and problem-based. I treat typically local keywords separately from service queries without a location modifier, which are often searched by users who are already in the given area. I also take into account what people actually call the service in practice, which language variants appear most often and whether it is worth building content around specific problems, not just around dry category names.
What matters most afterwards is assigning the keywords to the right pages and setting priorities. Not every service needs a separate page, but not every one can be sensibly combined with another without losing precision either. I look at the profitability of the services, the level of competition, the strength of the current domain and whether the company wants to win contacts quickly or to build a longer-term content presence in parallel. As a result, the keyword plan is not an abstract document but the basis for decisions about what to write, which pages to strengthen and where the local context should be shown directly.
Designing the page architecture
A well-designed site architecture puts in order not only SEO but also the way the website sells. I set out which pages should act as the main service pages, which are worth developing as separate specialisations, and where it is better to use supporting sections instead of multiplying almost identical URLs. On local sites it is particularly important not to create empty pages for a city just so that they “exist”, but to build a structure that really answers the user’s questions, shows the scope of the service and leads naturally to contact.
More and more often, the architecture should also be designed with discoverability beyond the classic list of results in mind. If a website has clear service names, readable sections, sensible headings, short answers to the key questions and logical connections between topics, it is easier to interpret not only for the search engine, but also for systems that generate answers on the basis of many sources. That is why, when designing the structure, I take into account not only SEO for keywords, but also whether the content can be quickly understood, quoted and linked to a specific service, location and user intent.
On-page and local implementation
On-page implementation usually covers more than improving a few tags. I work on page titles, headings, service descriptions, internal linking, the order of sections, the content that supports the purchase decision and the visibility of contact details. If the website is too general, I sharpen the communication so that every important page has its own role and is matched to a specific group of queries. In a local context it is also important to show the area served, the terms of service, the forms of contact and the information that builds credibility without resorting to advertising slogans.
Implementation does not end with the website, however. Depending on the situation, I add off-site work, put the local signals in order, develop supporting content and make sure the communication is consistent in the places where the brand is already visible. If the goal is better readability in AI-generated answers, I work on the content structure, the precision of the service definitions, question-and-answer sections and consistency of naming. This approach does not guarantee exposure in AI Overviews or chatbots, but it increases the chance that the site will be easier to understand, quote and associate with a specific topic.
