SEO, Social & AI Discoverability

Why the directory is built for discovery

The single biggest search advantage of this plugin is structural: every integration you publish becomes its own indexable page on your own domain, at a clean URL like /integrations/{slug}. Search engines and AI answer engines can crawl, index, and cite each listing individually — the same way they treat any other page on your site. That is fundamentally different from a hosted directory that lives on someone else’s subdomain, where the ranking authority accrues to the host rather than to you.

On top of that structural win, the plugin ships a built-in SEO and social pack that adds machine-readable data to each integration page so that Google, social networks, and AI search can understand exactly what each listing is. The pack is on by default — you do not need to configure anything to benefit from it.

What the built-in pack adds

On every published integration detail page, the plugin outputs the following into the page head.

SoftwareApplication structured data (JSON-LD)

Each integration page emits a SoftwareApplication JSON-LD block. This is the piece that helps Google and AI answer engines classify your listings as software products rather than generic blog posts. The plugin only includes fields it actually has data for, so the block stays accurate:

• name — the integration’s title.
• url — the integration’s page on your site.
• description — from the meta description resolution described below.
• image — the logo, or the first screenshot as a fallback.
• sameAs — the integration’s Website URL (the Visit Website target), linking the listing to the vendor’s own site.
• applicationCategory — the integration’s first assigned category.

The JSON-LD block is additive: it is emitted even when a dedicated SEO plugin is active, because those plugins do not describe your integrations as software applications.

Meta description, Open Graph, and Twitter Card tags

The plugin also adds a standard meta name="description" tag plus a set of Open Graph and Twitter Card tags so your listings look right when shared on social platforms and messaging apps. These include og:type, og:title, og:description, og:url, og:site_name, and og:image, along with the matching twitter:card, twitter:title, twitter:description, and twitter:image tags.

The share image is the integration’s logo (its featured image); if there is no logo, the plugin falls back to the first screenshot in the gallery. When an image is present the Twitter card uses the large summary_large_image style; otherwise it uses the compact summary style.

Heads up: unlike the JSON-LD, these meta, Open Graph, and Twitter tags are only emitted when no dedicated SEO plugin is active. See SEO-plugin awareness below.

The Meta description field and its fallback chain

The description used across all of the above comes from a single field in the integration editor. In the Details box you will find a Meta description field, labeled “SEO, optional.” Whatever you type there is the preferred description for that integration.

If you leave it blank, the plugin resolves a description automatically, in this order:

1. The explicit Meta description field, if you filled it in.
2. Otherwise the integration’s Preview Text.
3. Otherwise the first ~32 words of the integration’s main content, with shortcodes and HTML stripped.
4. Otherwise your site’s tagline.

Because a good description feeds the meta tag, the Open Graph and Twitter descriptions, and the JSON-LD description all at once, it is worth writing a deliberate one- or two-sentence summary in the Meta description field for your most important integrations. For where these fields live in the editor, see Building an Integration and Richer Integration Profiles.

Turning the pack on or off

The pack is controlled by a single setting. Go to Integrations > Settings, and on the Settings tab find the SEO & Social Tags checkbox (option intplugin_seo_tags). It is checked by default. Uncheck it and save if you want the plugin to stop emitting all of the above — for example if another tool already handles everything, including structured data for your integrations.

Developers can also force the pack off in code with the intplugin_seo_enabled filter (returning false suppresses the entire output regardless of the checkbox). There is no filter needed to turn it on — the checkbox is the switch.

SEO-plugin awareness

The plugin is aware of the major WordPress SEO plugins and deliberately avoids stepping on them. If any of the following are active, the plugin skips its own meta description, Open Graph, and Twitter tags so you never get duplicate tags fighting each other:

• Yoast SEO
• Rank Math
• All in One SEO
• SEOPress
• The SEO Framework

In that situation your SEO plugin owns the meta and social tags — which is what you want, since it is where you manage titles and social previews site-wide. The one thing the plugin still emits is the SoftwareApplication JSON-LD, because those SEO plugins do not generate that schema for your integrations. So you get the best of both: your SEO plugin’s meta and social handling, plus the integration-specific structured data.

What the pack does not do

The pack is focused on per-integration structured data and social tags. It does not generate XML sitemaps, and it does not manage site-wide SEO (page titles for non-integration pages, redirects, breadcrumbs, robots directives, and so on). Keep a dedicated SEO plugin — or rely on WordPress core, which produces a basic sitemap at /wp-sitemap.xml — for sitemaps and everything site-wide. The two work well together thanks to the awareness described above.

Practical tips

• Fill in Preview Text and the Meta description on your key integrations. Even the automatic fallbacks work, but a hand-written description reads better in search results and social shares.
• Give every integration a logo. The logo is the featured image and doubles as the social share image and the JSON-LD image; without one, the plugin falls back to the first screenshot, and without either there is no share image at all.
• Set descriptive alt text on the logo image in the Media Library so the image is meaningful to search engines and assistive technology.
• Set the Website URL in the Details box — it becomes the JSON-LD sameAs link that ties your listing to the vendor’s own site.
• Submit your /integrations page to Google Search Console and let the individual integration pages get discovered from there. Because each listing is a real URL on your domain, they can be crawled and indexed like any other page.

Related articles

• Building an Integration — where the Preview Text, Meta description, logo, and Website URL fields live.
• Richer Integration Profiles — screenshots, video, and resources that make each indexable page more complete.