Blazor error shows up in search results

vanillajonathan commented 1 year ago

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug

Google and Bing shows up the Blazor error message div in search results.

    <div id="blazor-error-ui">
        An unhandled error has occurred.
        <a href="" class="reload">Reload</a>
        <a class="dismiss">🗙</a>
    </div>

Expected Behavior

Search engines should not present content the Blazor error div element in the search results.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

7.0.2

Anything else?

Maybe there could be a hidden attribute on the blazor-error-ui div element, but I don't know if that would help.

Alerinos commented 1 year ago

Use data-nosnippet https://developers.google.com/search/docs/advanced/robots/robots_meta_tag#data-nosnippet-attr

I think you can add it in the documentation and the default template. Can I do a PR?

ghost commented 1 year ago

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

SpaceShot commented 11 months ago

I see that modifying the templates wasn't accepted as the way to proceed now, but this is still listed as help wanted. Is this a better documentation fix right now? What is the advice for this?

ghost commented 9 months ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

ghost commented 6 months ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

dotnet / aspnetcore