Asky SEO & GEO

Asky SEO & GEO is the WordPress side of Asky, the AI search visibility platform. SEO is how your site shows up in search engines; GEO, generative engine optimization, is how it shows up in the answers of ChatGPT, Perplexity, Gemini and Google's AI Mode. Asky measures both, finds what to fix, and this plugin applies the fixes you approve: technical SEO fields, structured data and the server logs that show which AI crawlers visit your site. It adds a small REST API under /wp-json/asky/v1 that your Asky account calls with the Application Password you already connected. It does nothing on its own: every change starts with a person approving it in Asky. What it does:

• Technical SEO fixes. Writes page titles, meta descriptions and Open Graph text into the fields of your SEO plugin (Yoast SEO, Rank Math or SEOPress) on posts, pages and custom post types, and image alt text where your pages store it (the editor content, Thrive Architect, Elementor, the featured image, the media library, synced patterns). Without an SEO plugin it keeps the values itself and prints the tags. The page cache is cleared after each change (LiteSpeed Cache, WP Rocket, SiteGround Optimizer, W3 Total Cache, WP Super Cache).
• Structured data. Registers the asky_json_ld post field and prints the JSON-LD block Asky attaches when it publishes a post.
• Server logs. On hosts that keep daily access log archives beside the WordPress install (SiteGround), lets Asky read them so AI crawler visits show up in your Asky crawler log reports. Reading is off until Asky switches it on for a connected site, and off again when you disconnect.

How connecting works: There is no key to paste into the plugin. Asky connects with a WordPress Application Password (WordPress 5.6 or later, HTTPS required), created for an administrator or editor in one of two ways:

• Approve on your site. In Asky, under Connections, WordPress, enter your site address. Asky sends you to your own WordPress admin, which asks you to approve Asky, creates the Application Password itself and returns you to Asky. Nothing is copied by hand.
• Paste an Application Password. In your WordPress profile, under Application Passwords, create one named for Asky and paste it into the same dialog.

Asky tests the connection before saving it. Either way, the password appears in your WordPress profile and you can revoke it there at any time, which cuts Asky off immediately. The full guide is at https://docs.askylabs.com/connections/wordpress. How access works:

• Every route needs a signed-in WordPress user. Reading or writing a post needs edit rights on that exact post. Server logs need an administrator.
• The plugin sends nothing anywhere. It makes no outbound request of its own: Asky calls your site, your site never calls Asky.
• Every part of the plugin can be switched off for a site with a constant in wp-config.php: ASKY_DISABLE_SEO_FIELDS (titles, descriptions, Open Graph), ASKY_DISABLE_IMAGE_ALT, ASKY_DISABLE_IMAGE_ALT_PATTERNS, ASKY_DISABLE_JSON_LD, ASKY_DISABLE_LOGS, or with the asky_modules filter. Asky then offers that fix by hand instead.

1.3.0

• Site defaults: one setting for every page that lacks the same thing. A self-referencing canonical, a default share image (og:image) and the site's structured data (Organization and WebSite) are added only to pages that print none of their own, so your SEO plugin and theme always win. Needs an Administrator.

1.2.0

• Viewport: when the theme prints no viewport tag, Asky can add the standard one (width=device-width, initial-scale=1) so pages fit phone screens, and take it out again. Needs an Administrator; block themes, which get the tag from WordPress, are left alone.

1.1.0

• Canonical address, indexing settings (noindex, nofollow, nosnippet, noimageindex, noarchive) and Open Graph image of a post, written to Yoast SEO, Rank Math or SEOPress, or printed by the plugin when no SEO plugin is active. A canonical can only name an address on the site itself.
• Redirects: a permanent redirect from an address that no longer exists to the page that replaced it. It answers only where WordPress would show a 404, so it never takes over a live page.
• robots.txt: Asky can replace the robots.txt WordPress serves, and hand it back. Needs an Administrator; a robots.txt file in the site root is left alone.

1.0.0

• First public release in the WordPress plugin directory. Everything below, verified on Yoast SEO, Rank Math and SEOPress.

0.5.0

• Server logs: read the host's daily access log archives for Asky's crawler log reports.
• Structured data: register the asky_json_ld field and print the JSON-LD block on singular pages.
• Modules can be switched off per site.

0.4.0

• Image alt text in synced patterns, once for every page using them.

0.3.0

• Image alt text where the page stores the image: editor content, Thrive Architect, Elementor, featured image, media library.

0.2.0

• Open Graph title and description. Titles and descriptions on sites without an SEO plugin.

0.1.0

• Titles and meta descriptions in Yoast SEO, Rank Math and SEOPress on every post type.