Query Alteration Settings & AIl in One Transport

  • Resolved ontheroad

    (@ontheroad)


    3 months, 1 week ago

    Hi Sybre,

    I’m looking to jump from All in One SEO. Couple of questions that are hanging on a little.


    The Query Alteration Settings: Your plugin is by default already generating fewer queries compared to others (well done on that). I use Google search instead of WP search on my site – I’m presuming it’s okay to ignore this setting in this case?

    Transport: your extension. Is it fully compatible with exporting and importing from All in One’s latest update? Reason I’m asking is a few of the other plugins had issues with the meta title (missing). I used the transporter plugin (not yours) in the end to transport from All in one to Framework and it seemed to work well though a few titles still skipped. Wondering if your Transport Plugin is good for the latest All in One update?

    Social Schema: Is it possible to add more? If so, how? I’m looking to include links like

    “sameAs”: [
    “https://www.linkedin.com/in/xxx”,
    “https://www.amazon.com/stores/xx”,
    “https://x.com/xx”,
    “https://www.facebook.com/x”,
    “https://www.instagram.com/x”,
    “https://www.youtube.com/user/x”,
    “https://www.pinterest.com/x”,
    “https://medium. etc

    Sitemap: archives, is it possible to disable them? I know there’s an optimized option but, I’m ultimately looking for posts only.

    Apologies for the long post, but I think you know how it is when you are making a switch like this!

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    3 months, 1 week ago

    Hello!

    I understand! You can keep the questions coming!

    1. The Query Alteration feature won’t affect Google Search-embedded results; it only affects WordPress’s on-site search results. You can toggle off “Enable search query alteration” to hide the relevant toggles from the page SEO settings.

    2. When importing data to TSF, you must not use any other SEO data transport plugin besides that of Extension Manager. The reason is that we need to perform syntax transformations before storing them; otherwise, you get wrong results.

    Unfortunately, when I wanted to implement support for AIOSEO, they changed their data structure, so I held off. The dust seems to have settled, and I have it planned for the next large update (probably March 2026).

    Until then, you could use Yoast SEO to import from AIOSEO. You should delete AIOSEO’s data via Yoast SEO’s importer. After that, you can use Transport to import from Yoast SEO.

    Always make a backup before transporting! Before using Extension Manager’s Transport, I recommend deactivating the other SEO plugins so they won’t repopulate their data.

    3. At “SEO Settings > Schema.org Settings > Connected Social Pages,” you can use any field to put any link you’d like. For a future major update, where I rework the settings page, I’m considering an automatically-iterating field so you can add thousands of links.

    Still, I don’t think it helps to fill in those fields — no search engine actually acknowledges them. In a past update I hid those fields, but reintroduced them because people were left confused about where to put those links.

    4. The optimized sitemap already doesn’t display archives. If you’re asking about the Core sitemaps (which activate when the optimized sitemap is disabled), then no, there’s no setting to hide taxonomy archives from those. You could use this filter to disable them:

    add_filter(
	'wp_sitemaps_add_provider',
	fn( $provider, $name ) => in_array( $name, [ 'taxonomies', 'users' ], true )  ? null : $provider,
	10,
	2,
);

    But I recommend using the optimized sitemap instead. Perhaps, for your use-case, we have historical sitemaps planned for large sites with millions of URLs, which will be part of a future major update.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.