perf(seo): koniec ze zmiana adresu CSS przy kazdym commicie - #254
Merged
Merged
Conversation
Search Console crawl stats, read today for the first time: 25% of Googlebot's requests on this site are CSS, and only 10% of all requests are discovery. Two of fifty-three pages carry 78% of impressions and thirty-six pages are not indexed at all, while the crawler spends a quarter of its budget re-reading normalize.css. The cause is one Liquid expression. The stylesheet href appended site.github.build_revision - the commit SHA - so every commit produced a different URL for a file that had not changed. Thirty commits in two days is thirty stylesheets as far as a crawler is concerned. It was buying nothing, and that was checked against the live response rather than reasoned about: GitHub Pages serves this with Cache-Control max-age=600 and an ETag. Without any buster the worst case is a ten-minute-old stylesheet, and the ETag usually prevents even that. The buster was solving a problem the CDN had already solved, and charging the crawl budget for it. Worth noting what this does not fix. Position is the real problem - the two pages carrying the impressions sit at 36 and 54, which is page four and page six - and no amount of crawl budget moves that. This frees the budget to find the pages that are already written; ranking them is the HP and IIS work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Statystyki indeksowania z Search Console, przeczytane dziś pierwszy raz: 25% żądań Googlebota na tym serwisie to CSS, a wykrywalność to zaledwie 10% wszystkich żądań.
Dwie z pięćdziesięciu trzech stron niosą 78% wyświetleń, 36 stron nie jest zaindeksowanych wcale — a robot spędza ćwierć budżetu na ponownym czytaniu
normalize.css.Przyczyna to jedno wyrażenie Liquid
Adres arkusza doklejał
site.github.build_revision— SHA commita — więc każdy commit produkował inny URL dla pliku, który się nie zmienił. Trzydzieści commitów w dwa dni to dla robota trzydzieści arkuszy stylów.I nie kupował nic
Sprawdzone na żywej odpowiedzi, nie wyrozumowane:
GitHub Pages już obsługuje świeżość. Bez bustera najgorszy przypadek to arkusz sprzed dziesięciu minut, a
ETagzwykle zapobiega nawet temu. Buster rozwiązywał problem, który CDN już rozwiązał — i kazał za to płacić budżetowi indeksowania.Czego to NIE naprawia
Prawdziwym problemem jest pozycja. Dwie strony niosące wyświetlenia siedzą na 36 i 54 — czwarta i szósta strona wyników — i żadna ilość budżetu indeksowania tego nie ruszy.
To uwalnia budżet, żeby robot znalazł strony, które już są napisane. Wypozycjonowanie ich to robota z HP i IIS.