When you search something like computer repair Christchurch and you see a competitor showing multiple results, it usually is not a trick. It means Google can find several distinct pages on that domain that each satisfy a slightly different intent.
This guide explains what is happening, and a practical way to build the same effect on your own site without turning it into spam.
The useful mental model is a bookshelf, not a stack of copies. A homepage introduces the business. A service page answers a buying or enquiry question. A location page connects that service to a place. A checklist or workflow article helps someone understand the problem before they contact you. When those pages are genuinely different, Google can choose the best page for each search instead of treating the site as one thin brochure.
If you want a quick example of the pattern, compare a service page like Computer repair (Christchurch) with a supporting workflow article like Computer repair workflow. Different intent, same topic cluster, and both help.
What you are seeing
Google is ranking page types, not just domains
On many searches, Google is choosing between several page types: a homepage, a service page, a location page, a checklist, a FAQ, or a guide. If your site only has a homepage and a contact page, Google has less to work with.
- Service page: what you do, who it is for, and what happens next.
- Location/service area page: a local summary that matches how people search (for example, Christchurch).
- Supporting article: a workflow, checklist, or common-problems guide that answers questions before someone calls.
- Proof and trust: consistent business details, helpful about page, and clear contact paths.
Search result shape
Why one domain can appear more than once
Google may show several pages from the same domain when each result has a different job. For a local tech business, that could mean the homepage for brand trust, a computer repair page for service intent, a Christchurch page for location intent, and a troubleshooting article for early research intent.
You cannot force Google to show a set of sitelinks or multiple organic results. You can make it more likely by giving the crawler a clean structure: descriptive URLs, useful headings, consistent navigation, relevant internal links, and no near-duplicate pages competing with each other. The site should feel like one connected knowledge base, not a pile of doorway pages.
Multiple results vs sitelinks
There are two different effects people often mix together
Sometimes one domain earns several separate organic results on the same search page. Other times Google shows sitelinks: extra shortcuts grouped underneath one main result. They look similar from a business-owner point of view because both make one domain feel larger in the results, but they are not controlled in the same way.
Separate organic results
These usually happen when different URLs answer different intents: homepage, service page, location page, pricing guide, workflow article, or FAQ.
Sitelinks
Google's systems may cluster shortcuts under a result when the site structure, headings, titles, and internal links make useful shortcuts obvious.
What you can influence
You cannot manually choose the exact display, but you can improve page titles, headings, navigation, internal links, and page distinctness.
What you should not chase
Do not create pages purely to force a result shape. Build pages that would still be useful if Google showed only one of them.
NZ SME reality
Why this matters for local search in Aotearoa
A lot of local intent searches are not just "brand name". People search by problem plus place. If you have one good Christchurch service page, Google might show it. If you have that plus a practical checklist and a workflow guide, Google has more options to show your site for different searches.
In practice, your goal is not "more pages". It is more useful pages with clear overlap and clear differences.
A simple blueprint
What to build first (without duplicating content)
Start with one service and build a small cluster around it. Keep each page focused on a single job.
- 1. One strong service page: "computer repair Christchurch", "IT support Christchurch", or whichever service matters most.
- 2. One workflow article: "how triage works", "what to check before you drop it off", "how we avoid data loss".
- 3. One checklist article: a printable list someone can follow, with a clear disclaimer that it is general guidance.
- 4. One FAQ block: add 6 to 10 real questions to the service page (not generic sales copy).
For this site, that pattern is visible in the services overview, computer repair page, computer repair reading path, and related troubleshooting articles. The same cluster approach can be repeated for Microsoft 365, domains and email, networking, source archive, and search basics.
Example cluster
How to model a competitor-style result set without copying them
A competitor may have a homepage, a general service page, and a location-specific page all ranking together. The useful response is not to copy their URLs. It is to map the search intents and build a cleaner set of pages that fit your own business.
Brand or homepage intent
Use the homepage for identity, broad service summary, trusted links, and clear routes into the most important page clusters.
Service intent
Use the service page to answer "can you help with this problem?", including workflow, scope, limitations, local context, and next step.
Location intent
Use a location/profile page when the local angle is real. It should add local context, not just repeat the service page with a city name.
Research intent
Use articles for checklists, troubleshooting workflows, buying decisions, setup mistakes, and questions people search before contacting someone.
Build order
A safe order for growing the search surface
If the site is small, build depth before breadth. One complete cluster is easier for Google and visitors to understand than ten half-finished service pages. After each page goes live, check that it is linked from the right hub and that it links back to the next useful step.
- Pick one priority service cluster, such as computer repair, IT support, Microsoft 365, DNS/email, networking, or SEO foundations.
- Write or improve the main service page so it has a specific audience, workflow, service area, contact path, and related resources.
- Add one supporting workflow article and one supporting checklist article, both linked from the service page and topic hub.
- Create or strengthen a topic hub so related pages are discoverable without relying only on the sitemap.
- Update the sitemap, inspect the live URL, and record the date so Search Console movement can be judged later.
Technical hygiene
Make it easy for Google to understand your site
The quiet stuff matters. Google cannot rank what it cannot crawl, and it struggles when pages look duplicated or disconnected.
- Every page needs a clear title, one H1, a meta description, and a self-referencing canonical URL.
- Use a sitemap and keep it current. Then use Search Console to request indexing for your most important pages.
- Link related pages together in the body copy (not just the nav). Explain why the link is relevant.
- Keep business details consistent across your website and any directory listings you control.
Applied example
A clean same-domain cluster map
On this site, the goal is not to make duplicate pages. It is to give Google and visitors several useful entry points into different intents: service, location, setup, troubleshooting, and technical proof. These pages should reinforce each other while still standing on their own.
Canonical discipline
Multiple results need distinct pages, not duplicate URLs
Canonicals, internal links, and sitemap URLs should all point at the preferred version of each page. If two pages are too similar, Google may treat one as a duplicate or choose a different canonical than the one you expected. That is useful when the pages are genuine duplicates; it is a problem when a page was meant to serve a distinct search intent but does not yet have enough unique value.
Distinct title and H1
The service page, location page, and article should each have titles and headings that describe different jobs.
Different body evidence
Use unique examples, workflow steps, FAQs, service boundaries, and internal links rather than changing only the city or keyword phrase.
Consistent canonical URL
Use the same preferred URL in the canonical tag, sitemap, internal links, and deployment notes.
Indexing check
If Search Console flags duplicate or canonical issues, compare the visible pages side-by-side before publishing more pages.
Common mistakes
What causes thin results (and how to avoid it)
The fastest way to waste effort is to publish five pages that say the same thing. Google often chooses one and ignores the rest.
- Do not spin near-duplicate location pages for every suburb unless each page has a real purpose.
- Do not publish generic "SEO tips" that do not connect back to your real services and local audience.
- Do not hide the basics: contact, service area, and what you actually do.
- Do not create pages only to capture a keyword if you cannot make the page useful on its own.
For background on the site and how these pages are structured, see About John Finnerty, the technology services overview, the Projects hub, the websites and search basics reading path, and the technical article hub.
Official references
Source rules behind this approach
These Google references are useful guardrails: sitelinks are automated, internal structure matters, canonical signals should be consistent, and missing pages need links or sitemap discovery paths.