"crawled - currently not indexed" Error when using Blazor WebAssembly #64346
Unanswered
Abdulrhman5
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have an ASP.NET Core Razor Pages website where most pages are purely server-rendered, and they’re all indexed by Google just fine. However, I have three pages that contain Blazor WebAssembly components, and these pages are crawled but not indexed by Google Search Console (Crawled - currently not indexed). And when I try to "REQUEST INDIXING" through GSC. I get the following error: "Oops! Something went wrong We had a problem submitting your indexing request. Please try again later."
Here’s an example page that throws an error when trying to request indexing:
I’m aware that Google doesn’t execute or index client-side Blazor (WebAssembly) content, but in this case, I'm concerned with the HTML that is already rendered on the server, not client-side Blazor.
What I’ve tried:
<component type="typeof(Core.Blazor.KeyboardContainer)" render-mode="WebAssembly" />And the problem presisted. So I guess the error is occurring because I am loading a ton of wasm files through this line<script src="~/_framework/blazor.webassembly.js"></script><script src="~/_framework/blazor.webassembly.js"></script>and the error cleared.What can I do to index pages that are server-side rendered HTML and contain Blazor client-side?
Beta Was this translation helpful? Give feedback.
All reactions