mohsinapexdigitalco
Forum Replies Created
-
A quick way to narrow this down before the conflict test: check whether the answers are actually being saved, or just not rendering in the editor.Open one of the affected posts, switch to the Code editor (the three-dot menu in the top-right → Code editor, or Ctrl+Shift+Alt+M), and look for the Yoast FAQ block markup in the post content. The questions and answers are stored there as block attributes.If the answers are present in the code but don’t show in the visual editor, it’s a rendering issue — usually a JavaScript conflict from another plugin or the theme. If the answers are missing from the code too, then the save itself isn’t persisting them, which points more toward a server-side problem (something interfering with the REST API save).That distinction tells you whether to look at editor scripts or the save pipeline, and it takes about a minute to check.
No, having posts split across post-sitemap.xml and post-sitemap2.xml won’t cause any problems — that’s exactly how sitemap indexes are meant to work.The sitemap_index.xml file at your domain root lists every individual sitemap, and Google discovers and crawls all of them through that index. It doesn’t expect everything in a single file. Google itself allows up to 50,000 URLs per sitemap file, while Yoast uses a conservative default limit of 1,000 per sitemap, which is why yours split into two files. Both files are treated identically when you submit the index in Search Console.On the count: sitemap files only include posts that are indexable. Anything set to noindex, redirected, canonicalized to another URL, or excluded in the plugin settings is left out by design — so the first file having fewer posts than your total is normal, and actually what you want. A sitemap that lists URLs your meta robots say shouldn’t be indexed would be the real problem.So you can leave it exactly as it is.
You’re not missing anything in the generator — Rank Math handles Organization schema differently from the per-post templates.The Schema Generator on individual posts and pages is only for page-level schema types (Article, FAQ, HowTo, Product, etc.). Organization (or Person) schema is configured once, site-wide, and Rank Math then outputs it automatically in the schema graph on every page.To set it up, go to Rank Math → Titles & Meta → Local SEO and set the Knowledge Graph Type to Organization, then fill in the organization’s name, logo, and other details there. From that point on, Rank Math emits an Organization node in the JSON-LD on every page, and your per-post schemas (like Article) link to it as the publisher through the graph’s @id references.So you don’t need to add it per post — one global setup covers the whole site. After saving, view the source of any page and look for the JSON-LD script to confirm the Organization node is there.
A few WordPress-specific things worth checking beyond what you’ve done: (1) In GSC, inspect one affected URL and read the exact status — “Discovered – currently not indexed” vs “Crawled – currently not indexed” point at different causes. (2) For service businesses, location/service pages often trip on near-duplicate content — if your airport pages are near-identical, Google may crawl but refuse to index the thinner ones; differentiate the copy. (3) Check page-level index settings in your SEO plugin — sometimes a template or category default sets noindex. (4) Internal links matter more than sitemaps: make sure affected pages are linked from your nav or homepage, not only in the sitemap. (5) Check the sitemap’s lastmod dates — a stale lastmod can deprioritise recrawls. Don’t resubmit unchanged URLs; fix, then request indexing on a few samples.