feat(seo): miejsca na weryfikacje Google i Bing, i powod dla ktorego to wazne - #248
Merged
Merged
Conversation
…y matter The owner asked whether we could find people's fresh Google queries and email them. The premise does not hold: search queries are not public. Nobody sees who searched for what, there is no dataset of them to harvest, and that is a fact about how search works rather than a rule about what is allowed. But there is a real thing underneath the question, and we do not have it. Search Console reports the actual queries that brought somebody to this site. It is the only legitimate source for that information, because it is the only place the real queries appear at all - in the console of the site they landed on. Checked rather than assumed: docs.msgwing.com is verified with Yandex and with neither Google nor Bing. Seventeen error pages went up this week aimed at a December traffic spike, and there is currently no way to see whether any of them rank for anything. Verification moves from a hardcoded tag to _config.yml, so a token is pasted in one place instead of edited into the layout, and an empty value emits no tag - a half-configured entry cannot ship a broken one. None of the three can use DNS TXT. docs.msgwing.com is a CNAME, required for GitHub Pages, and a name carrying a CNAME can hold no other record type (RFC 1034). Yandex's resolver enforces that and never looks; Google's and Cloudflare's serve it anyway, which is why the existing tag is HTML and the new ones have to be too.
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
1 participant
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.
Właściciel zapytał, czy da się znaleźć świeże zapytania ludzi w Google i napisać do nich maila.
Przesłanka nie działa: zapytania wyszukiwarek nie są publiczne. Nikt nie widzi, kto czego szukał, nie istnieje zbiór takich danych do pozyskania — i to jest fakt o tym, jak działa wyszukiwarka, a nie reguła o tym, co wolno.
Ale pod spodem jest rzecz realna i jej nie mamy
Search Console pokazuje prawdziwe zapytania, po których ktoś trafił na tę stronę. To jedyne legalne źródło tej informacji, bo to jedyne miejsce, w którym prawdziwe zapytania w ogóle się pojawiają — w konsoli serwisu, na który ktoś wszedł.
Sprawdzone, nie założone:
Siedemnaście stron błędów stanęło w tym tygodniu, wycelowanych w grudniowy skok, i nie mamy jak zobaczyć, czy którakolwiek na cokolwiek rankuje.
Co się zmienia
Weryfikacja przenosi się z tagu na sztywno do
_config.yml— token wkleja się w jednym miejscu, a pusta wartość nie emituje tagu wcale, więc półskonfigurowany wpis nie może wysłać zepsutego.Żadna z trzech nie może użyć DNS TXT:
docs.msgwing.comto CNAME wymagany przez GitHub Pages, a nazwa z CNAME nie może nieść innego typu rekordu (RFC 1034).