Summary

This file will allow Google to verify we own the site at docsify.js.org. Then we will have access to the indexing tools. Once this is in place, I will figure out how it works, then I will see how to give maintainers access.

The idea is that, with #1968 enabling history router, we are one step closer to full SEO on Google. By connecting to the Google SEO inspector, I will be able to see how well the site is indexable in history mode, then we'll know what to do next if we need to improve.

What kind of change does this PR introduce?

Repo settings

For any code change,

• Related documentation has been updated if needed
• Related tests have been updated or tests have been added

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

Related issue, if any:

Tested in the following browsers:

• Chrome
• Firefox
• Safari
• Edge
• IE

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docsify-preview	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 10, 2024 11:41pm

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 854ffbc:

Sandbox	Source
docsify-template	Configuration

We have the Google Analytics in our site, are they the same thing? But I have never accessed to that place tho.

I check this doc below.

https://support.google.com/webmasters/answer/9008080?hl=en#zippy=%2Cgoogle-analytics-tracking-code

2133644

Meta and file conflict?
I'll contact him and see if he can share the permissions.

@trusktr I invited you, please check your gmail. In that case, can this PR be closed?

@sy-records Hey, the Google Analytics is actually different from the Search Console. Looks like this:

It's been verified and I'll invite you guys.

js-org/js.org#9079