What it is.
Technical search work, content architecture and the newer job of being quotable by AI assistants. Both are built into every website we ship and run as an ongoing programme where it earns its place.
Search is a compounding asset rather than a campaign. The pages built this quarter keep earning for years, which is why the architecture matters more than the tricks.
What you get.
- Technical search foundations
- Content and page architecture
- Structured data and entity work
- AI search infrastructure
- Local and map presence
- Reporting and tracking
How an engagement runs.
The audit
We crawl the site, pull the query and index data, and map every page against what it should rank for. The output is a scored list of problems and openings, ordered by the revenue sitting behind them.
Technical repair
Crawl errors, index bloat, redirect chains, slow templates and broken schema get fixed at the code level by the same team that builds our websites. You get a changelog of what was altered and why.
Pages and structure
We build the pages the query data says are missing: services, the suburbs you work in, the questions buyers type before they call. Each is written from your own work, marked up so search engines and assistants can read it, and linked into the site.
Authority and iteration
Then we earn the mentions that make rankings hold: trade press, listings, supplier and association pages. Every month the query data reorders the backlog, so the plan follows what is moving rather than what we assumed at the start.
What arrives, and when.
- The monthly report
- A written read on which queries moved, what those positions sent to the site and what those visits turned into, with the reasoning rather than a dashboard screenshot.
- Live dashboard access
- Looker Studio pulling from your own Search Console and Analytics, so you can check positions, clicks and enquiries any day of the week without asking us for an update.
- The working backlog
- A prioritised list of technical fixes, pages to build and pages to rewrite, kept current so you can see what is in progress and what is queued behind it.
- Published work
- Service pages, location pages, articles and schema shipped to your site, each one logged against the query it was built to win.
- The monthly call
- A working session on what changed, what we're doing next, and anything happening in your business that should redirect the plan.
Questions we get asked.
Who owns the accounts, the data and the pages?
You do, from day one. Search Console, Analytics, the domain, the CMS logins and every page we write sit in your accounts under your business name, and we work inside them as users you can remove. If you ever move on, nothing needs migrating, because nothing was ever held somewhere else. The site keeps its history and its rankings.
Who actually does the work?
The same team that does everything else here. Technical work, content, internal linking and digital PR are all made in-house, so the person writing your service pages sits beside the one fixing your crawl errors. Nothing is subcontracted, and you'll know the people on your account by name.
How does the work start?
We audit before touching anything. Crawl and index coverage, site speed, the internal link graph, how your service and location pages are structured, and what the query data says people type when they need your work. That becomes a prioritised backlog, and the fixes with the clearest path to enquiries go first. You see the list before we act on it.
How is the work measured?
Against revenue rather than activity. We track the queries that carry buying intent, where you sit on them, what those positions send to the site, and what those sessions do once they arrive: quote requests, calls, form fills and the jobs that trace back to them. Rankings appear in the report because they explain the movement, not because they're the point.
What happens if we stop?
The work stays with you, because it was always in your accounts. Pages, schema, the technical fixes and any coverage earned remain on your site and keep working. Positions don't reset the day the work stops, though they soften as pages age and other sites keep publishing against the same queries. We hand over the backlog and the reasoning behind it, so whoever picks it up isn't starting blind.
What does being cited by AI assistants actually involve?
Assistants answer from pages they can parse and sources they've seen corroborated elsewhere, so the work is structural as much as editorial. Clean markup. Schema that describes what you actually do, a business record that matches across the web, and answers written plainly enough to be quoted back. We track which prompts return you, which return nobody useful, and what sits on the page when a citation shows up.
The rest of the suite.
Contact the Ignis Team
Send through your details and we will audit your business before we reply.