OGEEAT

No. OGEEAT complements SEO plugins. It automatically defers its Open Graph output when a compatible SEO plugin already manages those tags. JSON-LD remains independent so you can keep OGEEAT's E-E-A-T graph or disable it under OGEEAT > Settings when another plugin should own all schemas.

OGEEAT keeps one canonical /llms.txt and one /llms-full.txt at the site root, whatever the language setup (directories, subdomains or one domain per language). On a multilingual site the file opens with the list of languages and their home URLs, then gives each language its own section with the site name in that language, its pages and posts in their original language, and closes with interaction rules asking AI assistants to answer in the language of the question and not to mix languages. No separate /en/llms.txt file is created. A wpml-config.xml file lets WPML (and Polylang) translate the free-text settings such as the llms.txt title, description and footer.

Yes. Use the ogeeat_llms_post_description filter. It receives the resolved description and the WP_Post object, so a developer can return a custom field for selected post types without changing post_excerpt.

Yes. Use the ogeeat_llms_post_content filter. It receives the resolved body, the WP_Post object and the configured word limit, so a developer can serve a summary written for AI from a custom field. The returned value is written as is, so sanitize and trim it. The filter never runs on password-protected or excluded content.

Insert the [ogeeat_share] shortcode where the buttons should appear, for instance in a Toolset, ACF or page builder content template, then set their position to "Manual only (shortcode)" under OGEEAT > Settings > AI, GEO & Firewall so they are not also added automatically. Optional attributes: style="stacked" and label="...". To hide them on a single page, such as the home page, tick "Hide the Share with AI buttons on this content" in its OGEEAT box: the shortcode follows that choice too. Developers can use the ogeeat_ai_share_display filter. The automatic insertion only targets the body of the content, never a custom field displayed through the_content: if a template does not display the body at all, for instance a page built only from fields, use the shortcode.

Google lets each signed-in reader choose preferred sources: content from those sites shows up more often in Top Stories, with a "Preferred" badge, and in AI Mode and AI Overviews. Turn the module on under OGEEAT > Settings > AI, GEO & Firewall. Google accepts a domain or a subdomain, never a folder: the "Check eligibility" link opens Google's tool for your domain. Nothing is requested from Google until a reader clicks the button, and the button stays a plain link to Google when JavaScript is off. Choose "Card" for a larger block with an explanation and a preview, "Compact" for one line. Under the Share with AI buttons the button is always one line; tick "Also add a line under the Share with AI buttons" to have both, the line there and the card below the content. To place it yourself, use the [ogeeat_preferred_source] shortcode, with optional style="compact" or style="card" and label="..." attributes. Both styles take the fonts and colors of your theme; to adjust them, set --ogeeat-preferred-source-accent, --ogeeat-preferred-source-radius or --ogeeat-preferred-source-card-radius in your theme's CSS. The Google preferred source button looks like a plain link A page optimizer removed its stylesheet. OGEEAT marks the stylesheet and the script of the button so that LiteSpeed Cache leaves them alone: update to 2.7.1 or later, then purge the cache. With another optimizer, exclude preferred-source.css from the "remove unused CSS" feature and preferred-source.js from the delayed JavaScript, then purge the cache. The Google window reloads my article instead of closing Your site most likely sends the Cross-Origin-Opener-Policy: same-origin header. It cuts the link between the article and the Google window, so Google cannot report back: after "Add", the window loads the article again, with #__WA_RES__ in its address, and no confirmation appears. Use same-origin-allow-popups instead, or remove the header: the page stays protected from other sites that open it, and its own windows can answer it. The header usually comes from a security plugin, the host, a Cloudflare rule or the server configuration. The Google Preferred Sources section of OGEEAT > Settings > AI, GEO & Firewall checks this header, and a Content Security Policy that would block https://news.google.com. The link to Google works in every case.

Yes. The existing ogeeat_geo_checks filter can replace or extend the FAQ check for custom blocks. A ready-to-use example is included on the OGEEAT Documentation screen.

E-E-A-T means Experience, Expertise, Authoritativeness and Trustworthiness. GEO means Generative Engine Optimization: structuring content so AI engines can understand and cite it. OGEEAT exposes identity signals and evaluates each post with 12 citability checks.

Yes. OGEEAT is GPL software with no premium version or subscription.