Technical SEO gets the pages crawled, indexed and kept.
Technical SEO is the work that decides whether a URL can be crawled, stored and shown for the query you meant. We read the coverage report, fix the paths and the canonicals, then check the same report again instead of guessing.
What we mean by technical SEO
A page can be well written and still never appear. Google has to find the URL, fetch it, decide it is the one to keep, and keep it. Technical SEO is that chain: crawl paths, status codes, canonicals, indexation rules, internal links and the speed measures that sit under Core Web Vitals.
We treat indexation as the first result. Rankings come after a page is in the index. If Search Console says a URL was discovered and not indexed, or crawled and not indexed, writing another paragraph will not fix it. The crawl has to be able to reach the page, and the page has to be the one you want kept.
SEO, GEO and AEO, togetherVideojam search resultsGenerative engine optimizationAnswer engine optimization
The first three steps are a one-day snapshot and the last two a 28-day window, so the step from indexed to shown compares two different periods.
- Known to Google: 2,445 pages (Coverage snapshot, 23 Oct 2026)
- Crawled: 2,068 pages (Coverage snapshot, 23 Oct 2026)
- Indexed: 970 pages (Coverage snapshot, 23 Oct 2026)
- Shown in search, 28 days: 810 pages (Performance, 4–31 Oct 2026)
- Clicked, 28 days: 77 pages (Performance, 4–31 Oct 2026)
How we do it
We start from the property you already have in Search Console, not from a generic checklist. The first pass is coverage: how many pages are indexed, how many are not, and which reason each excluded URL carries. Then we look at the internal links, because a page with no in-body links is easy to miss and easy to drop.
The fixes are specific. A noindex that was left on a template. A canonical that points at a sibling and splits the signals. A redirect chain. A 404 that is still in the sitemap. Two URLs competing for the same query, which is cannibalisation: we pick the URL that should rank and point the other one at it, or we merge them.
After the fix we wait for a fresh crawl and read the same coverage export. We do not call a change finished because it was deployed. Finished means the indexed count moved, or we can say plainly that it did not and why.
- Export coverage and name every not-indexed reason.
- Trace internal links and remove dead ends.
- Set one canonical per query and drop the duplicate.
- Recheck the same report after Google recrawls.
What Videojam’s coverage report showed
Videojam is a site we built and still run. On 23 October 2026 the coverage export showed 970 indexed pages and 1,475 that were not indexed. The not-indexed reasons were: excluded by noindex 367, crawled but not indexed 632, discovered but not indexed 377, alternate with a canonical elsewhere 92, not found 6, redirect 1.
Those six reasons are the job. noindex is a choice, and it should be a choice you meant. Crawled-not-indexed and discovered-not-indexed are the piles where Google saw the URL and declined to keep it, often because the page is thin, duplicated, or poorly linked. The 92 alternates are a canonical decision. The 6 not-found URLs and the 1 redirect do not belong in an indexable sitemap.
The performance chart for 1 August to 31 October 2026, the same window, is 272 clicks and 12,486 impressions on web search. On 22 September the property recorded 0 clicks and 13 impressions. On 23 September it recorded 4 clicks and 133 impressions. That is the day after crawl-path and event-hub work shipped. The two dates line up. We call that a correlation. We do not claim the deploy caused the jump, because Search Console cannot prove that from a chart.
| Status | Pages |
|---|---|
| Indexed | 970 |
| Excluded by noindex | 367 |
| Alternate, canonical elsewhere | 92 |
| Not found (404) | 6 |
| Redirect | 1 |
| Crawled, not indexed | 632 |
| Discovered, not indexed | 377 |
- Impressions
- 17,469
- Clicks
- 342
- CTR
- 1.96%
- Avg. position(lower is better)
- 21.2
- vs previous 28 days
- The export starts on 1 August, so there is no earlier period to compare.
Impressions (left axis)Clicks (right axis)22 Sept: Crawl-path and event-hub work shipped
The rise starts the next day. A correlation, not proof of cause.
Show the numbers as a table
| Date | Impressions | Clicks | Avg. position |
|---|---|---|---|
| 1 Aug 2026 | 19 | 0 | 41.9 |
| 2 Aug 2026 | 24 | 0 | 35.3 |
| 3 Aug 2026 | 14 | 0 | 39.3 |
| 4 Aug 2026 | 10 | 0 | 38.8 |
| 5 Aug 2026 | 7 | 0 | 36.3 |
| 6 Aug 2026 | 14 | 0 | 33.6 |
| 7 Aug 2026 | 7 | 0 | 31.4 |
| 8 Aug 2026 | 6 | 0 | 37.7 |
| 9 Aug 2026 | 29 | 3 | 27.1 |
| 10 Aug 2026 | 19 | 1 | 31.6 |
| 11 Aug 2026 | 21 | 0 | 36.0 |
| 12 Aug 2026 | 12 | 0 | 43.7 |
| 13 Aug 2026 | 20 | 1 | 42.9 |
| 14 Aug 2026 | 14 | 4 | 33.1 |
| 15 Aug 2026 | 19 | 0 | 56.1 |
| 16 Aug 2026 | 22 | 0 | 59.4 |
| 17 Aug 2026 | 13 | 0 | 57.1 |
| 18 Aug 2026 | 20 | 0 | 47.9 |
| 19 Aug 2026 | 11 | 0 | 60.8 |
| 20 Aug 2026 | 15 | 1 | 42.9 |
| 21 Aug 2026 | 12 | 3 | 37.3 |
| 22 Aug 2026 | 18 | 0 | 68.4 |
| 23 Aug 2026 | 22 | 0 | 52.5 |
| 24 Aug 2026 | 19 | 3 | 39.2 |
| 25 Aug 2026 | 27 | 0 | 49.1 |
| 26 Aug 2026 | 26 | 0 | 50.0 |
| 27 Aug 2026 | 29 | 0 | 57.4 |
| 28 Aug 2026 | 34 | 0 | 58.9 |
| 29 Aug 2026 | 31 | 0 | 52.7 |
| 30 Aug 2026 | 34 | 1 | 54.4 |
| 31 Aug 2026 | 29 | 0 | 54.8 |
| 1 Sept 2026 | 13 | 0 | 36.8 |
| 2 Sept 2026 | 18 | 2 | 25.9 |
| 3 Sept 2026 | 13 | 1 | 40.5 |
| 4 Sept 2026 | 16 | 1 | 41.2 |
| 5 Sept 2026 | 14 | 1 | 40.0 |
| 6 Sept 2026 | 24 | 0 | 41.3 |
| 7 Sept 2026 | 20 | 0 | 46.5 |
| 8 Sept 2026 | 16 | 0 | 42.8 |
| 9 Sept 2026 | 27 | 0 | 53.4 |
| 10 Sept 2026 | 23 | 0 | 24.4 |
| 11 Sept 2026 | 26 | 0 | 47.7 |
| 12 Sept 2026 | 26 | 1 | 52.4 |
| 13 Sept 2026 | 22 | 1 | 46.5 |
| 14 Sept 2026 | 26 | 1 | 55.6 |
| 15 Sept 2026 | 21 | 0 | 54.0 |
| 16 Sept 2026 | 24 | 0 | 47.8 |
| 17 Sept 2026 | 12 | 1 | 29.2 |
| 18 Sept 2026 | 13 | 0 | 46.8 |
| 19 Sept 2026 | 13 | 0 | 50.0 |
| 20 Sept 2026 | 11 | 1 | 48.8 |
| 21 Sept 2026 | 10 | 0 | 56.3 |
| 22 Sept 2026 | 13 | 0 | 59.2 |
| 23 Sept 2026 | 133 | 4 | 22.8 |
| 24 Sept 2026 | 185 | 2 | 21.8 |
| 25 Sept 2026 | 206 | 6 | 16.7 |
| 26 Sept 2026 | 194 | 4 | 16.9 |
| 27 Sept 2026 | 163 | 4 | 14.4 |
| 28 Sept 2026 | 167 | 4 | 12.2 |
| 29 Sept 2026 | 222 | 7 | 18.8 |
| 30 Sept 2026 | 193 | 7 | 19.5 |
| 1 Oct 2026 | 196 | 5 | 22.7 |
| 2 Oct 2026 | 218 | 8 | 16.1 |
| 3 Oct 2026 | 214 | 4 | 18.9 |
| 4 Oct 2026 | 255 | 1 | 19.4 |
| 5 Oct 2026 | 223 | 3 | 15.6 |
| 6 Oct 2026 | 237 | 5 | 16.5 |
| 7 Oct 2026 | 244 | 3 | 19.9 |
| 8 Oct 2026 | 232 | 2 | 16.7 |
| 9 Oct 2026 | 253 | 7 | 14.1 |
| 10 Oct 2026 | 231 | 1 | 14.5 |
| 11 Oct 2026 | 248 | 3 | 20.3 |
| 12 Oct 2026 | 269 | 4 | 15.6 |
| 13 Oct 2026 | 306 | 5 | 18.6 |
| 14 Oct 2026 | 359 | 7 | 17.9 |
| 15 Oct 2026 | 387 | 8 | 18.7 |
| 16 Oct 2026 | 441 | 4 | 19.2 |
| 17 Oct 2026 | 389 | 5 | 22.6 |
| 18 Oct 2026 | 357 | 6 | 19.9 |
| 19 Oct 2026 | 408 | 7 | 19.1 |
| 20 Oct 2026 | 332 | 8 | 20.7 |
| 21 Oct 2026 | 404 | 7 | 19.1 |
| 22 Oct 2026 | 456 | 15 | 20.2 |
| 23 Oct 2026 | 508 | 24 | 20.2 |
| 24 Oct 2026 | 458 | 15 | 17.0 |
| 25 Oct 2026 | 356 | 7 | 24.3 |
| 26 Oct 2026 | 348 | 10 | 17.6 |
| 27 Oct 2026 | 375 | 6 | 21.4 |
| 28 Oct 2026 | 335 | 9 | 21.2 |
| 29 Oct 2026 | 344 | 3 | 18.4 |
| 30 Oct 2026 | 316 | 10 | 21.2 |
| 31 Oct 2026 | 326 | 5 | 20.4 |
| 1 Nov 2026 | 344 | 7 | 18.3 |
| 2 Nov 2026 | 317 | 4 | 21.0 |
| 3 Nov 2026 | 359 | 7 | 22.5 |
| 4 Nov 2026 | 343 | 6 | 22.2 |
| 5 Nov 2026 | 335 | 6 | 21.3 |
| 6 Nov 2026 | 332 | 4 | 21.1 |
| 7 Nov 2026 | 356 | 2 | 24.6 |
| 8 Nov 2026 | 328 | 3 | 24.3 |
| 9 Nov 2026 | 307 | 8 | 23.9 |
| 10 Nov 2026 | 327 | 7 | 23.6 |
| 11 Nov 2026 | 347 | 6 | 20.0 |
| 12 Nov 2026 | 397 | 0 | 20.6 |
| 13 Nov 2026 | 891 | 10 | 18.1 |
Internal links and cannibalisation
Internal links are how you tell Google which pages matter and which query each one owns. We count in-body links, not the navigation and not the footer. A page that only appears in the menu is one click from everywhere and still easy to treat as chrome. A page linked from the body of related pages is part of the subject.
Cannibalisation is the opposite problem: two indexable URLs aimed at one query. The fix is not “add more content” to both. The fix is to choose. One URL stays. The other canonicalises, redirects, or is rewritten so it answers a different question. We do that from the query report, not from a hunch about titles.
What we will not promise
We will not promise a ranking, a traffic number, or a date when a page will be indexed. Indexation is Google’s decision. What we can show is the before and after of the coverage report, the URLs we changed, and the queries those URLs already receive.
We also will not invent a competitor’s figures or a benchmark for “average” indexation. The only coverage numbers on this page are Videojam’s, from the export dated 23 October 2026. If your site’s report looks different, the work starts from your export, not from this one.
What you get from us is a written read of that export, not a 40-point checklist. We name the not-indexed reasons in your numbers, the URLs we would change first, and whether each change is a canonical, a noindex you did not mean, a redirect, or an internal link. If most of the excluded URLs are noindex on purpose, we say so and we stop. Turning those pages on would be the wrong job. If the pile is crawled-but-not-indexed, the next work is the links and the duplication. A plugin will not decide which URL should own a query. The chart on this page is the Videojam web property for the three months, with the 22 September mark drawn on it. The day-by-day table under the chart is the same series, so the drawing is not the only copy of the numbers.
We will not promise a ranking, a traffic number, or a citation in an AI answer. You get the audit, the changes, and a second read of the same Search Console export, so the before and after sit on one page. If the indexed count does not move, we say that too.
Technical SEO questions
What is technical SEO?
Technical SEO is the set of changes that let a search engine crawl a URL, choose it over its duplicates, and keep it in the index. It covers status codes, canonicals, indexation rules, internal links, sitemaps and Core Web Vitals. It is not a promise that a page will rank.
How do you tell if a page is indexed?
We use the Search Console coverage export, not a site: query. The export says indexed or not, and if not, it gives a reason: noindex, crawled but not indexed, discovered but not indexed, an alternate canonical, a 404 or a redirect.
What did Videojam’s coverage report say?
On 23 October 2026 Videojam had 970 indexed pages and 1,475 not indexed. The largest not-indexed reasons were crawled but not indexed (632), discovered but not indexed (377) and noindex (367).
Did a deploy cause Videojam’s impression jump?
We don’t know. Crawl-path and event-hub work shipped around 22 September 2026, when the property had 0 clicks and 13 impressions. The next day it had 4 clicks and 133 impressions. That is a correlation. The chart does not prove cause.
What is cannibalisation?
Cannibalisation is two indexable URLs competing for the same query. We pick the URL that should own it and canonicalise, redirect or rewrite the other one. Adding more copy to both pages usually makes the split worse.
Do you guarantee rankings?
No. We report what changed in Search Console: indexed counts, the reasons pages were excluded, and the clicks and impressions on the queries you already have. Anyone who guarantees a position is guessing.
Tell us what you're launching.
Book a 20-minute intro call, or email a few lines about what you're launching. We'll reply with a rough plan and a price range, whether or not we end up working together.
Or write to hello@audacian.eu
Proof
Search Console growth
Videojam Search Console, since August (1 Aug 2026–13 Nov 2026): 17,469 impressions, 342 clicks, 1.96% CTR. Latest 28 days (17 Oct 2026–13 Nov 2026): 10,695 impressions, 207 clicks, 1.94% CTR.
10,695 impressions · 28 daysVideojam SEO
How Videojam is structured so search and AI answers can cite it.
970 pages indexedADE archive
Videojam’s ADE 2026 coverage and the festival archive.