Comparing the HTML your server sent against the page after rendering shows that a large share of the text is added by JavaScript. Readers and Googlebot see the full page; assistants that do not execute scripts see the smaller version, and will summarise your page based on whatever fraction arrived in the response.
The server sends a skeleton and the body text is fetched and inserted client-side, often from an API call after load.
Move the main content into the server response. Client-side fetching is fine for things that genuinely depend on the viewer, such as a cart or a personalised panel, but the article, the product description and the headings should be in the HTML:
// Instead of fetching the article after mount,
// render it on the server and hydrate:
export async function getServerSideProps() {
const article = await getArticle();
return { props: { article } };
}The response body is the only version of your page some crawlers will ever see. Putting the substance there means everyone reads the same page.
This issue can affect your site's search engine rankings and user experience. Addressing it promptly helps ensure optimal performance and visibility in search results.
bseoa automatically checks for this warning during site analysis, along with hundreds of other technical SEO issues.
Choose the license that fits your needs and start getting the deep, actionable insights you deserve.