-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add google indexing troubleshooting #13265
feat: add google indexing troubleshooting #13265
Conversation
Hi @patrickhousley 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. Gatsby Cloud will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 20 to 30 minutes). |
src/content/docs/browser/new-relic-browser/troubleshooting/google-indexing-unknown-paths.mdx
Outdated
Show resolved
Hide resolved
…gle-indexing-unknown-paths.mdx Co-authored-by: Jordan Porter <silentsummitsoftware@gmail.com>
src/content/docs/browser/new-relic-browser/troubleshooting/google-indexing-unknown-paths.mdx
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from a Browser Agent perspective
I just updated from develop because this was stalled. |
✅ docs-website-develop deploy preview ready
|
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
Adding a troubleshooting document for the browser agent around the possible existence of 404 errors in customer's Google Search dashboards.