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

Videojam’s indexation funnelPages at each stage. Coverage report of 23 Oct 2026 (known = 970 indexed + 1,475 not indexed; crawled = known minus 377 discovered but never crawled), then pages with impressions and with clicks in the 28-day export (4–31 Oct).

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.

  1. Known to Google: 2,445 pages (Coverage snapshot, 23 Oct 2026)
  2. Crawled: 2,068 pages (Coverage snapshot, 23 Oct 2026)
  3. Indexed: 970 pages (Coverage snapshot, 23 Oct 2026)
  4. Shown in search, 28 days: 810 pages (Performance, 4–31 Oct 2026)
  5. 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.

Indexed pages and why the rest were not indexed, 23 Oct 2026970 pages indexed. 1,475 not indexed. The reasons below are the not-indexed bucket only: noindex 367, crawled but not indexed 632, discovered but not indexed 377, alternate with a canonical 92, 404 6, redirect 1.
StatusPages
Indexed970
Excluded by noindex367
Alternate, canonical elsewhere92
Not found (404)6
Redirect1
Crawled, not indexed632
Discovered, not indexed377
Videojam search performance1 Aug–13 Nov 2026 · Google Search Console, web search
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

002501050020750301,000401 Aug1 Sept1 Oct1 Nov22 Sept

The rise starts the next day. A correlation, not proof of cause.

Show the numbers as a table
DateImpressionsClicksAvg. position
1 Aug 202619041.9
2 Aug 202624035.3
3 Aug 202614039.3
4 Aug 202610038.8
5 Aug 20267036.3
6 Aug 202614033.6
7 Aug 20267031.4
8 Aug 20266037.7
9 Aug 202629327.1
10 Aug 202619131.6
11 Aug 202621036.0
12 Aug 202612043.7
13 Aug 202620142.9
14 Aug 202614433.1
15 Aug 202619056.1
16 Aug 202622059.4
17 Aug 202613057.1
18 Aug 202620047.9
19 Aug 202611060.8
20 Aug 202615142.9
21 Aug 202612337.3
22 Aug 202618068.4
23 Aug 202622052.5
24 Aug 202619339.2
25 Aug 202627049.1
26 Aug 202626050.0
27 Aug 202629057.4
28 Aug 202634058.9
29 Aug 202631052.7
30 Aug 202634154.4
31 Aug 202629054.8
1 Sept 202613036.8
2 Sept 202618225.9
3 Sept 202613140.5
4 Sept 202616141.2
5 Sept 202614140.0
6 Sept 202624041.3
7 Sept 202620046.5
8 Sept 202616042.8
9 Sept 202627053.4
10 Sept 202623024.4
11 Sept 202626047.7
12 Sept 202626152.4
13 Sept 202622146.5
14 Sept 202626155.6
15 Sept 202621054.0
16 Sept 202624047.8
17 Sept 202612129.2
18 Sept 202613046.8
19 Sept 202613050.0
20 Sept 202611148.8
21 Sept 202610056.3
22 Sept 202613059.2
23 Sept 2026133422.8
24 Sept 2026185221.8
25 Sept 2026206616.7
26 Sept 2026194416.9
27 Sept 2026163414.4
28 Sept 2026167412.2
29 Sept 2026222718.8
30 Sept 2026193719.5
1 Oct 2026196522.7
2 Oct 2026218816.1
3 Oct 2026214418.9
4 Oct 2026255119.4
5 Oct 2026223315.6
6 Oct 2026237516.5
7 Oct 2026244319.9
8 Oct 2026232216.7
9 Oct 2026253714.1
10 Oct 2026231114.5
11 Oct 2026248320.3
12 Oct 2026269415.6
13 Oct 2026306518.6
14 Oct 2026359717.9
15 Oct 2026387818.7
16 Oct 2026441419.2
17 Oct 2026389522.6
18 Oct 2026357619.9
19 Oct 2026408719.1
20 Oct 2026332820.7
21 Oct 2026404719.1
22 Oct 20264561520.2
23 Oct 20265082420.2
24 Oct 20264581517.0
25 Oct 2026356724.3
26 Oct 20263481017.6
27 Oct 2026375621.4
28 Oct 2026335921.2
29 Oct 2026344318.4
30 Oct 20263161021.2
31 Oct 2026326520.4
1 Nov 2026344718.3
2 Nov 2026317421.0
3 Nov 2026359722.5
4 Nov 2026343622.2
5 Nov 2026335621.3
6 Nov 2026332421.1
7 Nov 2026356224.6
8 Nov 2026328324.3
9 Nov 2026307823.9
10 Nov 2026327723.6
11 Nov 2026347620.0
12 Nov 2026397020.6
13 Nov 20268911018.1

Get a free 20-min SEO and AI-search review of your site

We open your site and Search Console with you and point at what is holding it back.

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.