WEBVTT

1
00:00:00.225 --> 00:00:08.675
You're listening to how one site cut its weight from fourteen point five megabytes to just one, boosting its browsing score to a perfect hundred.

2
00:00:08.675 --> 00:00:11.875
Written by Angel Nee-evess on Promptway.

3
00:00:12.410 --> 00:00:18.360
My homepage weighed 14.5 megabytes and took 43 seconds to paint its largest element on a mid-range phone.

4
00:00:18.360 --> 00:00:32.060
I found this out the same week I sat down to make the site ready for AI search, which turned out to be a useful coincidence, because the single biggest thing you can do for AI visibility in twenty twenty six is the same thing you could have done for Google in twenty fifteen: make the site fast, structured, and honest.

5
00:00:32.385 --> 00:00:33.185
This is the audit

6
00:00:33.185 --> 00:00:33.347
I

7
00:00:33.347 --> 00:00:33.722
ran

8
00:00:33.722 --> 00:00:33.860
on

9
00:00:33.860 --> 00:00:34.060
my

10
00:00:34.060 --> 00:00:34.360
own

11
00:00:34.360 --> 00:00:34.760
site,

12
00:00:34.760 --> 00:00:34.897
with

13
00:00:34.897 --> 00:00:35.010
the

14
00:00:35.010 --> 00:00:35.472
numbers

15
00:00:35.472 --> 00:00:35.772
each

16
00:00:35.772 --> 00:00:36.085
fix

17
00:00:36.085 --> 00:00:36.685
bought.

18
00:00:36.685 --> 00:00:36.822
The

19
00:00:36.822 --> 00:00:37.072
full

20
00:00:37.072 --> 00:00:39.847
playbook with every command is on my site.

21
00:00:39.847 --> 00:00:40.885
What follows is the

22
00:00:40.885 --> 00:00:43.410
part that transfers to yours.

23
00:00:43.685 --> 00:00:45.410
S E O, A E O, GEO:

24
00:00:45.410 --> 00:00:45.547
what

25
00:00:45.547 --> 00:00:45.635
the

26
00:00:45.635 --> 00:00:46.022
letters

27
00:00:46.022 --> 00:00:46.460
actually

28
00:00:46.460 --> 00:00:46.685
buy

29
00:00:46.685 --> 00:00:47.860
you

30
00:00:47.860 --> 00:00:50.260
The acronyms read like three strategies.

31
00:00:50.260 --> 00:00:52.960
They are one strategy with three layers.

32
00:00:53.235 --> 00:00:58.060
S E O is the base: indexable pages, clean metadata, fast loads, working links.

33
00:00:58.060 --> 00:01:05.122
A E O, answer engine optimization, is S E O plus structured answers: content organized so a model can quote a specific, correct chunk of it.

34
00:01:05.122 --> 00:01:14.960
GEO, generative engine optimization, is A E O plus machine-readable discovery for engines that are not Google: feeds, L L M S dot text, IndexNow, explicit crawler permissions.

35
00:01:15.285 --> 00:01:16.385
You do not pick one.

36
00:01:16.385 --> 00:01:18.797
Each layer assumes the one below it.

37
00:01:18.797 --> 00:01:28.760
A site with perfect L L M S dot text files and a 14 MB homepage has built the roof before the foundation, which is exactly what I had done.

38
00:01:29.035 --> 00:01:36.160
What Google says NOT to do Google published actual guidance on AI search readiness, and the most useful part is the prohibition list.

39
00:01:36.160 --> 00:01:39.185
There is no special markup for AI Overviews or AI Mode.

40
00:01:39.185 --> 00:01:41.310
They use the same index as classic Search.

41
00:01:41.310 --> 00:01:51.985
Google explicitly advises against chunking your content into Q&A shards, rewriting prose to sound machine-friendly, piling on structured data beyond what earns a rich result, and chasing inauthentic backlinks.

42
00:01:52.260 --> 00:01:57.610
Read that list again, because half the "A E O services" being sold right now are on it.

43
00:01:57.885 --> 00:02:02.910
The scoreboard One Lighthouse run on the mobile homepage, before and after.

44
00:02:03.235 --> 00:02:30.335
Metric Before After Performance 63 73 Accessibility 95 100 Agentic browsing 67 100 Largest Contentful Paint 43.2 s 5.9 s Speed Index 6.2 s 3.6 s Total page weight fourteen thousand five hundred sixty one A ninety three percent weight cut and an eighty six percent LCP improvement, and not one of the fixes was clever.

45
00:02:30.610 --> 00:02:34.085
The fixes, in order of pain Discoverability first.

46
00:02:34.085 --> 00:02:39.385
My Search Console verification record lived in the wrong D N S host, so Google could not verify the domain.

47
00:02:39.385 --> 00:02:41.460
One text record in the right place fixed it.

48
00:02:41.460 --> 00:02:46.485
Then I set up IndexNow with a tiny script and a GitHub Action that pings Bing only when blog content changes.

49
00:02:46.485 --> 00:02:51.035
Bing matters more than it used to: it feeds ChatGPT's web search, Copilot, and DuckDuckGo.

50
00:02:51.035 --> 00:02:57.610
IndexNow turns "indexed within days" into "indexed within hours." Accessibility doubles as agent legibility.

51
00:02:57.610 --> 00:03:05.935
A components-level bug was rendering a fresh h1 for every project card, my canvas-dithered images were announcing empty alt text, and the logo link had no accessible name.

52
00:03:05.935 --> 00:03:16.372
That last one alone was worth 5 accessibility points and 33 agentic browsing points, because an agent walking the accessibility tree hit an unnamed link as the first interactive element on every page.

53
00:03:16.710 --> 00:03:20.460
One aria-label="Home" took both scores to 100.

54
00:03:20.460 --> 00:03:24.172
The accessibility tree is the interface agents actually read.

55
00:03:24.172 --> 00:03:26.460
Treat it like a public A P I.

56
00:03:26.885 --> 00:03:29.060
Performance was two embarrassing assets.

57
00:03:29.060 --> 00:03:34.635
A 3.3 MB background music MP3 loaded eagerly on every route, for a feature most visitors never turn on.

58
00:03:34.635 --> 00:03:43.085
Lazy-instantiating the audio on first toggle removed it from the critical path, and re-encoding the file itself, mono, 64 kbps, cover art stripped, cut it to 1.1 MB.

59
00:03:43.085 --> 00:03:48.997
Then the photos: fourteen JPEGs at 500 KB to 1.1 MB each, displayed at 400 pixels wide.

60
00:03:49.335 --> 00:03:55.922
Re-encoded to AVIF at the display size they went from 10.5 MB to 113 KB.

61
00:03:55.922 --> 00:03:59.797
That is a ninety nine percent reduction with no visible difference.

62
00:03:59.797 --> 00:04:05.985
Another 28 thumbnails went from 1.16 MB to 91 KB the same way.

63
00:04:06.310 --> 00:04:18.947
The stragglers: a modernized browserslist dropped 14 KB of polyfills nobody needed, the new LCP element got a priority hint, and a render-blocking Typekit stylesheet that served zero fonts got deleted.

64
00:04:18.947 --> 00:04:21.635
Every codebase has one of those.

65
00:04:21.910 --> 00:04:28.235
What I deliberately did not do No FAQPage or HowTo schema bolted onto pages that are not FAQs or how-tos.

66
00:04:28.235 --> 00:04:35.560
The five types I already ship, WebSite, Person, BlogPosting, BreadcrumbList, and CreativeWork, match the content; anything more is maintenance debt with no measured upside.

67
00:04:35.560 --> 00:04:40.222
No rewriting posts to sound machine-friendly: the blog reads like a human wrote it because a human does.

68
00:04:40.222 --> 00:04:45.760
And no third-party A E O submission services, which are the twenty twenty four era equivalent of directory spam.

69
00:04:46.035 --> 00:04:54.660
I also kept my L L M S dot text route while removing the inline copy from the page head, since Google confirmed it does not read the format and other engines only need the route.

70
00:04:54.660 --> 00:04:58.247
Promptway itself still ships the inline block for the engines that do read it.

71
00:04:58.247 --> 00:05:01.935
Reasonable sites can disagree here; the route is the part that matters.

72
00:05:01.935 --> 00:05:05.710
The content side of that stack is covered in the eight-layer guide.

73
00:05:05.985 --> 00:05:09.547
The takeaway There is no secret AI search lane.

74
00:05:09.547 --> 00:05:18.635
AI Overviews, AI Mode, ChatGPT browsing, Perplexity: they all reward the same boring fundamentals, just with less patience for bloat and broken semantics than human visitors have.

75
00:05:18.635 --> 00:05:23.247
If your site is fast, indexable, well structured, and useful, it is already AI search ready.

76
00:05:23.247 --> 00:05:28.735
Mine was not, and the gap was 13.5 megabytes of avoidable weight and one unlabeled link.

77
00:05:29.110 --> 00:05:32.260
Run the audit on your own site before you buy anything.

78
00:05:32.260 --> 00:05:36.285
If the numbers come back like mine did, the fix list will write itself.

79
00:05:36.285 --> 00:05:44.485
And if you want the agent to run the whole thing for you, the audit my agency does over M C P shows what that looks like on the paid side.

80
00:05:45.045 --> 00:05:45.895
That's the story.

81
00:05:45.895 --> 00:05:48.807
You'll find every source linked at the end of the article.

82
00:05:48.807 --> 00:05:51.470
Thanks for listening, on Promptway.