by
liorzabari
1 (0 reviews)
Scayla Connect
Connector for Scayla: measures whether AI assistants name your store, then writes SEO, FAQ schema and redirects, verified by read-back.
Scayla Connect ranks #49,836 among WordPress.org plugins with 1+ active installations, is #6,313 of 12,226 in the E-commerce category, a 1/5 rating from 0 reviews, and was last updated Sep 15, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.0.0
Current Version v1.0.0
Updated 20 hours ago
Last Update on 15 Sep, 2026
Refreshed 7 hours ago
Last Refreshed on
#6,313 of 12,226 in E-commerce
Actively maintained
Rank
#49,836
—
No change
Active Installs
1+
—
No change
KW Avg Position
N/A
—
No change
Downloads
0
+42 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
49,123
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 7 more installs to reach 10+
Rank Changes
Current
#49,836
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.0
- Last Updated
- Sep 15, 2026
- Requires WP
- 6.4+
- Tested Up To
- 7.1
- PHP Version
- N/A
- Author
- liorzabari
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,752
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,007
WooCommerce
7M+ installs
#6
MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)
2M+ installs
#25
ManageWP Worker
1M+ installs
#54
Google for WooCommerce
800K+ installs
#75
WooPayments: Integrated WooCommerce Payments
800K+ installs
#76
WooCommerce PayPal Payments
800K+ installs
#81
WooCommerce Stripe Payment Gateway
700K+ installs
#85
WooCommerce Tax (formerly WooCommerce Shipping & Tax)
500K+ installs
#115
Frequently Asked Questions
Common questions about Scayla Connect
Pairing creates one user, scayla-connector, holding a custom role with exactly 13 capabilities: read, edit_posts, edit_others_posts, publish_posts, edit_published_posts, delete_posts, delete_others_posts, delete_published_posts, edit_pages, edit_others_pages, edit_published_pages, upload_files, manage_categories. With WooCommerce active, 9 product capabilities are added, including read_private_products (WooCommerce maps a product collection read to it) and manage_product_terms. It does not get manage_options, install_plugins, install_themes, switch_themes, edit_theme_options, edit_users, unfiltered_html, publish_pages or delete_pages. Pages are editable but not publishable or deletable, because the service only writes SEO onto pages that already exist. The role is re-asserted on every load and any capability not on the list is stripped, so another plugin cannot quietly widen it.
No. The plugin never fetches, stores or evaluates remote code — no eval, no dynamic include, no remote file download. What arrives from Scayla is text: titles, descriptions, FAQ questions and answers, and paths. Each passes an explicit filter before storage: FAQ questions have all tags stripped and answers pass wp_kses_post; category and tag descriptions pass a post-context wp_kses allowlist extended only with details, summary and a small set of class/id/data- attributes, so script, iframe and on* handlers cannot be stored even if the token were stolen. Redirect paths pointing at another host are rejected outright.
It fails loudly. After every SEO write the plugin reconciles the provider's storage, re-reads the value from the source your front end will actually serve, and compares. If they differ it returns HTTP 500 with scayla_write_not_verified and a body containing the expected value, the actual value, which storage layer answered (indexable, postmeta, option or scayla) and a hint distinguishing "Yoast's indexable did not reconcile" from "another plugin may be overriding SEO meta". For Yoast terms the read-back deliberately reads the indexable rather than the option just written, because a verification that reads back its own write proves nothing.
Both are optional. Without WooCommerce it works on posts, pages, categories and tags; with it, products and product categories are covered too. Without Yoast or Rank Math it stores values in its own _scayla_seo_title and _scayla_seo_description meta and renders them through pre_get_document_title and a wp_head meta description. Those standalone renderers refuse to run unless the detected provider is exactly "none", so there is never a duplicate title alongside Yoast or Rank Math.
The redirect matcher runs at template_redirect and costs zero database queries when a request does not match: the map lives in one autoloaded option WordPress has already fetched, an empty map returns before the request URI is parsed, and only a hit touches the database. If the map would exceed 100 KB it is dropped in favour of a single prepared query, so a large table never bloats every admin and cron request. Paths are stored in utf8mb4_bin columns so matching is byte-exact, which stops a case-normalising rule such as /Page to /page from matching its own destination and looping forever. The plugin registers no cron jobs.
No. It is created with a 64-character random password that is never transmitted, displayed, stored in plaintext or logged — but the guarantee does not rest on that. An authenticate filter rejects any interactive login resolving to the service user, and an allow_password_reset filter refuses password resets for it, closing the otherwise real path of requesting a reset to connector@yourdomain on a catch-all mail domain. The token maps to the service user only on REST requests, anchored to the first path segment via rest_get_url_prefix(), so a front-end permalink merely containing wp-json cannot borrow the identity.
No. Every route has a real permission callback, including GET /health; there is no __return_true anywhere in the code. Write routes additionally check the specific object: current_user_can( 'edit_post', $id ) for that post, or term existence plus a taxonomy allowlist plus manage_categories for that term. The bulk read endpoint enforces authorisation per ID rather than once per batch, and anything the service user may not touch is returned in a skipped list instead of being read. Failed token attempts are rate-limited per IP, bucketed on REMOTE_ADDR rather than on spoofable proxy headers.
Click Disconnect on the Scayla admin page. The token hash is deleted immediately and every subsequent request from Scayla is rejected; your content, SEO values, FAQ data and redirects stay exactly as they are. Deactivating changes nothing else, so you can deactivate to troubleshoot and reactivate without re-pairing. Deleting the plugin removes the role from the service user, deletes the role, drops the redirects table, deletes _scayla_faq, _scayla_seo_title and _scayla_seo_description from every post and term, and sweeps every scayla_* option and transient — on every site of a multisite network. Two things are kept on purpose: the scayla-connector account, so content it authored keeps its author attribution (it has no role, zero capabilities and cannot be logged into; delete it manually if you prefer), and SEO values already written into Yoast or Rank Math, because at that point they are your site's meta, not the plugin's.
Yes. Network activation provisions every existing site, sites created afterwards are provisioned automatically, and uninstall walks every site so no orphan table or role is left behind.
