Sitemap is accepted, but my blog posts still aren’t indexed. What should I check?

An accepted sitemap means Google can read it, not that every URL will be indexed. Start with URL Inspection for a few affected posts and check the specific indexing status. “Discovered” and “Crawled” but not indexed point to different stages, so that detail is more useful than resubmitting the sitemap.

Also inspect the rendered page and response headers for a noindex directive, an unexpected canonical, or content that only appears after client-side rendering. A 200 response by itself doesn’t rule those out.

A blog-specific sitemap is fine as long as it’s valid and linked from robots.txt or otherwise discoverable. You can also use a sitemap index if you have multiple sitemap files. Check that the sitemap lists the final, preferred URLs, not redirects, duplicates, or pages you don’t want indexed.

For a couple of posts, compare the sitemap URL with the canonical shown in the page source and in Search Console. If they differ, fix that before chasing framework settings.

I’d look at the content and internal links next. If posts are very similar, thin, or hard to reach from the rest of the site, Google may choose not to index them even when crawling works. Make sure each post has useful, distinct material and links from relevant category pages or other articles.

There isn’t enough information here to conclude that the Vercel subdomain is the cause. A custom domain may be useful for a stable site identity, but it won’t by itself make pages indexable.

For dynamic Next.js pages, verify what a crawler actually receives, not just what you see in your browser. Check the rendered HTML for the article text, title, description, canonical, and robots meta tag. Also confirm that the sitemap is regenerated when new posts are published and that it contains their current URLs.

If URL Inspection reports a fetch or rendering problem, then investigate the route and deployment. If crawling succeeds and the page is eligible for indexing, the sitemap may be working as intended and the remaining decision is Google’s.