[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fSQWql98CdezVAbNIs5y_Ntu6CeKjjE3zdaIOjdou_EM":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"aetosseo","Aetos SEO","https:\u002F\u002Fprofiles.wordpress.org\u002Faetosseo\u002F",4,10,100,30,94,"2026-08-29T08:49:11.070Z",[14,35,51,64],{"slug":15,"name":5,"version":16,"author":5,"author_profile":6,"description":17,"short_description":18,"active_installs":8,"downloaded":19,"rating":20,"num_ratings":20,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":31,"download_link":32,"security_score":9,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"aetos-seo","4.0.12","\u003Cp>Aetos SEO is an \u003Cstrong>audit plugin\u003C\u002Fstrong>, not another meta-writer. It runs alongside\u003Cbr \u002F>\nyour existing SEO plugin (Rank Math, Yoast, AIOSEO, SEOPress, or any other)\u003Cbr \u002F>\nand tells you what is actually broken, missing, or risky across technical SEO\u003Cbr \u002F>\nand AI-readiness, then shows you a prioritized list of what to fix first.\u003C\u002Fp>\n\u003Cp>Think of it as a second opinion that does not touch your meta titles, your\u003Cbr \u002F>\nschema output, or your sitemap. It only reads, diagnoses, and reports.\u003C\u002Fp>\n\u003Ch4>Why a separate audit plugin?\u003C\u002Fh4>\n\u003Cp>Every SEO plugin tells you it is doing a great job. None of them tell you\u003Cbr \u002F>\nwhen something is wrong outside of their own scope: a noindex left from\u003Cbr \u002F>\nstaging, a canonical pointing at the wrong domain, a schema that is valid\u003Cbr \u002F>\nbut does not list the right entity, an \u003Ccode>\u003Ch1>\u003C\u002Fcode> that does not match the\u003Cbr \u002F>\ntitle, a robots.txt that blocks an AI crawler you actually want to be in,\u003Cbr \u002F>\nor a sitemap that omits half your category pages.\u003C\u002Fp>\n\u003Cp>Aetos SEO does that read across \u003Cstrong>the whole rendered page\u003C\u002Fstrong>, then ranks the\u003Cbr \u002F>\nfindings by severity so you can fix the highest-impact issues first.\u003C\u002Fp>\n\u003Ch4>What the free edition checks\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Technical SEO\u003C\u002Fstrong> – indexability, canonicals, robots directives, sitemap\u003Cbr \u002F>\npresence and freshness, redirects, broken links, HTTP error pages.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Crawl coverage\u003C\u002Fstrong> – what search engines and AI crawlers (GPTBot, PerplexityBot,\u003Cbr \u002F>\nClaude-Web, Google-Extended, etc.) can actually reach on your site.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>On-page\u003C\u002Fstrong> – titles, meta descriptions, heading structure, duplicate\u003Cbr \u002F>\npatterns, language and \u003Ccode>dir\u003C\u002Fcode> correctness for Arabic \u002F RTL sites.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mobile usability\u003C\u002Fstrong> – viewport, readability heuristics, tap target sanity.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Media\u003C\u002Fstrong> – missing alt text, oversized images, lazy-loading hints.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Structured data\u003C\u002Fstrong> – is valid JSON-LD present for Organization, Article,\u003Cbr \u002F>\nBreadcrumb? Are required fields filled?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AI-readiness (AEO \u002F GEO)\u003C\u002Fstrong> – is your content readable by AI answer engines?\u003Cbr \u002F>\nChecks AI-crawler access in robots.txt (GPTBot, ClaudeBot, PerplexityBot,\u003Cbr \u002F>\nGoogle-Extended and more), llms.txt presence, JSON-LD entity coverage\u003Cbr \u002F>\n(Organization, sameAs, author \u002F E-E-A-T, publisher), FAQ \u002F HowTo schema,\u003Cbr \u002F>\nH2 \u002F H3 passage structure for answer extraction, and Open Graph completeness.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Performance basics\u003C\u002Fstrong> – asset counts, cache headers, heavy CSS \u002F JS.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Analytics stack\u003C\u002Fstrong> – auto-detects GA4, Google Tag Manager, Microsoft\u003Cbr \u002F>\nClarity, and Meta Pixel.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security basics\u003C\u002Fstrong> – HTTPS, mixed content, exposed admin endpoints\u003Cbr \u002F>\n(informational).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What you actually see\u003C\u002Fh4>\n\u003Cp>Every finding includes: a plain-language title, a severity badge (High \u002F\u003Cbr \u002F>\nMedium \u002F Low \u002F Info), the pages where it was detected, an “Open” \u002F “Fixed”\u003Cbr \u002F>\nstatus, guidance on how to verify the fix, and a “why this matters”\u003Cbr \u002F>\nexplanation. Results are shown directly in the Findings screen.\u003C\u002Fp>\n\u003Ch4>Bilingual interface (Arabic and English)\u003C\u002Fh4>\n\u003Cp>The plugin auto-detects RTL sites and switches the admin interface to\u003Cbr \u002F>\nArabic. Finding titles, severity levels, and “why this matters” copy are\u003Cbr \u002F>\nall translated.\u003C\u002Fp>\n\u003Ch4>How it differs from Pro\u003C\u002Fh4>\n\u003Cp>Pro is sold separately at \u003Ca href=\"https:\u002F\u002Faetosseo.com\u002F\" rel=\"nofollow ugc\">aetosseo.com\u003C\u002Fa> and is\u003Cbr \u002F>\n\u003Cstrong>uploaded to your site by you\u003C\u002Fstrong>, like a separate premium add-on. The\u003Cbr \u002F>\nWordPress.org edition is a complete local audit tool: it shows every finding it\u003Cbr \u002F>\ncomputes in full, and you set the scan depth yourself in Settings (the default\u003Cbr \u002F>\nis 50 pages, or set 0 to analyze every page on your site).\u003C\u002Fp>\n\u003Cp>The WordPress.org edition \u003Cstrong>diagnoses\u003C\u002Fstrong> your technical SEO and AI-readiness.\u003Cbr \u002F>\nPro is for \u003Cstrong>acting on what it finds and going deeper\u003C\u002Fstrong>: advanced\u003Cbr \u002F>\nanswer-engine modules, industry modules, deeper content analysis, internal\u003Cbr \u002F>\npage-opportunity prioritization, AI handoff reports with copy-paste prompts\u003Cbr \u002F>\nfor any AI assistant, and agency-style HTML \u002F PDF \u002F CSV reports. Pro audits\u003Cbr \u002F>\nfrom inside WordPress too, and it does not connect your site to any external\u003Cbr \u002F>\nSEO, analytics, or AI service.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>The free edition does \u003Cstrong>not\u003C\u002Fstrong> automatically contact any third-party\u003Cbr \u002F>\nservice. Updates ship through WordPress.org like any other free plugin\u003Cbr \u002F>\n(handled by WordPress core, not by this plugin).\u003C\u002Fp>\n\u003Cp>During an audit, the plugin performs HTTP requests \u003Cstrong>against your own\u003Cbr \u002F>\nWordPress site\u003C\u002Fstrong> to inspect your public pages, robots.txt, sitemaps, and\u003Cbr \u002F>\ninternal links. These are same-site requests; no page content leaves your\u003Cbr \u002F>\nserver. To run audits in the background it may also trigger WordPress cron\u003Cbr \u002F>\nthrough a same-site loopback request to this same WordPress installation\u003Cbr \u002F>\n(the standard WP-Cron mechanism); this never contacts Aetos servers or any\u003Cbr \u002F>\nthird-party API in the free edition. The admin interface also contains a few\u003Cbr \u002F>\nuser-clicked links to documentation, pricing, changelog, and support on\u003Cbr \u002F>\naetosseo.com — those open only when you click them; the plugin never\u003Cbr \u002F>\nrequests those pages itself.\u003C\u002Fp>\n\u003Cp>Some checks look for analytics or tag-manager fingerprints already present in\u003Cbr \u002F>\nyour site’s rendered HTML. The plugin may recognize strings such as\u003Cbr \u002F>\ngoogletagmanager.com, google-analytics.com, analytics.google.com,\u003Cbr \u002F>\nconnect.facebook.net, clarity.ms, clarity.microsoft, plausible.io,\u003Cbr \u002F>\ncdn.plausible.io, cdn.segment.com, segment.com, posthog.com, matomo.js,\u003Cbr \u002F>\nmatomo.php, and piwik.js, plus the matching client-side API names these tools\u003Cbr \u002F>\nplace in page scripts (for example gtag, fbq, and _paq). These are\u003Cbr \u002F>\n\u003Cstrong>detection strings only\u003C\u002Fstrong>: Aetos SEO does not contact those providers, does\u003Cbr \u002F>\nnot send them data, and does not load their scripts. If your public pages\u003Cbr \u002F>\nalready include one of those scripts, the plugin records that it was detected\u003Cbr \u002F>\nso the audit can avoid false “analytics missing” findings.\u003C\u002Fp>\n\u003Cp>To put findings in context, the audit also detects which SEO, performance,\u003Cbr \u002F>\ncaching, security, and page-builder plugins or themes are active on your site\u003Cbr \u002F>\nand reads their settings from your \u003Cstrong>local\u003C\u002Fstrong> WordPress database through the\u003Cbr \u002F>\nstandard options API. This information is shown only inside your own WordPress\u003Cbr \u002F>\nadmin, to explain a finding (for example, that a caching plugin controls a\u003Cbr \u002F>\nheader the audit flagged). It is never transmitted anywhere, and the plugin\u003Cbr \u002F>\nnever contacts those plugins’ vendors.\u003C\u002Fp>\n","Technical SEO and AI-readiness auditor for WordPress. See what blocks your site in Google and in AI answers, with every finding shown in full.",413,0,"2026-07-13T22:24:00.000Z","7.0.2","6.2","7.4",[26,27,28,29,30],"ai-readiness","schema","seo","site-audit","technical-seo","https:\u002F\u002Faetosseo.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Faetos-seo.4.0.12.zip",null,"2026-07-22T17:31:50.256Z",{"slug":36,"name":37,"version":38,"author":5,"author_profile":6,"description":39,"short_description":40,"active_installs":20,"downloaded":41,"rating":20,"num_ratings":20,"last_updated":42,"tested_up_to":22,"requires_at_least":43,"requires_php":24,"tags":44,"homepage":49,"download_link":50,"security_score":9,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"aetos-arabic-search-normalizer","Aetos Arabic Search Normalizer","1.0.0","\u003Cp>Aetos Arabic Search Normalizer improves normal front-end WordPress searches for Arabic visitors.\u003C\u002Fp>\n\u003Cp>It keeps WordPress’s existing title, excerpt, and content matching, then adds a bounded normalized fallback for post titles and excerpts. For example, a search for \u003Ccode>احمد\u003C\u002Fcode> can find a title containing \u003Ccode>أَحْمَد\u003C\u002Fcode>, and \u003Ccode>مدرسه\u003C\u002Fcode> can find \u003Ccode>مدرسة\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>The normalizer handles these common differences:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Alef forms: ا, أ, إ, آ, and ٱ.\u003C\u002Fli>\n\u003Cli>Ta marbuta and ha: ة and ه.\u003C\u002Fli>\n\u003Cli>Ya and alef maqsura: ي and ى.\u003C\u002Fli>\n\u003Cli>Waw\u002Fya with hamza: ؤ and ئ.\u003C\u002Fli>\n\u003Cli>Common Arabic diacritics and tatweel.\u003C\u002Fli>\n\u003Cli>Common Persian keyboard forms for kaf and ya.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin works automatically with posts, pages, WooCommerce products, and other post types when their front-end search uses WordPress’s normal \u003Ccode>WP_Query\u003C\u002Fcode> search.\u003C\u002Fp>\n\u003Ch3>Performance boundaries\u003C\u002Fh3>\n\u003Cp>The plugin deliberately normalizes only the relatively short \u003Ccode>post_title\u003C\u002Fcode> and \u003Ccode>post_excerpt\u003C\u002Fcode> database columns. WordPress’s original \u003Ccode>post_content\u003C\u002Fcode> search remains active, but the plugin does not wrap full content in repeated SQL transformations.\u003C\u002Fp>\n\u003Cp>Enhancement is skipped and the exact core search is preserved for admin, REST, Ajax, attachment, excluded-term, unusually long, or more than six-term searches. These are performance and compatibility boundaries, not paid limits.\u003C\u002Fp>\n\u003Cp>The plugin creates no index, custom table, option, cookie, analytics record, scheduled task, REST route, or external request.\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>The plugin sends no data outside the site and stores no search terms, settings, cookies, analytics, or personal data.\u003C\u002Fp>\n","Improve Arabic title and excerpt matching across common letter and diacritic variations without indexing, tracking, or external services.",50,"2026-07-20T07:30:00.000Z","6.5",[45,46,47,48],"arabic","rtl","search","woocommerce","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Faetos-arabic-search-normalizer.1.0.0.zip",{"slug":52,"name":53,"version":38,"author":5,"author_profile":6,"description":54,"short_description":55,"active_installs":20,"downloaded":56,"rating":20,"num_ratings":20,"last_updated":57,"tested_up_to":22,"requires_at_least":43,"requires_php":24,"tags":58,"homepage":49,"download_link":63,"security_score":9,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"aetos-saudi-checkout-regions","Aetos Saudi Checkout Regions for WooCommerce","\u003Cp>Aetos Saudi Checkout Regions for WooCommerce helps Saudi-focused WooCommerce stores reduce free-text checkout address mistakes.\u003C\u002Fp>\n\u003Cp>When WooCommerce classic checkout is used, the plugin adds Saudi administrative regions to the state field and turns the city field into a city selector for Saudi Arabia. Other countries keep the normal WooCommerce city field.\u003C\u002Fp>\n\u003Cp>The first release focuses on Saudi Arabia only. It works locally inside WordPress, does not call any external service, does not collect analytics, and does not write directly to WooCommerce order tables.\u003C\u002Fp>\n\u003Cp>Built by the team behind Aetos SEO at NSR Elmtagr Digital Marketing.\u003C\u002Fp>\n\u003Cp>Main features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Saudi Arabia region list for WooCommerce address fields.\u003C\u002Fli>\n\u003Cli>City choices grouped by selected Saudi region.\u003C\u002Fli>\n\u003Cli>Arabic or English labels, with automatic selection from the site locale.\u003C\u002Fli>\n\u003Cli>Settings page to enable or disable the checkout enhancement.\u003C\u002Fli>\n\u003Cli>HPOS-friendly behavior because WooCommerce stores the normal checkout fields.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Important scope note: version 1.0.0 targets WooCommerce classic checkout. It does not modify WooCommerce Checkout Blocks.\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>Aetos Saudi Checkout Regions for WooCommerce does not collect personal data, does not track users, and does not send checkout data to external services.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin does not connect to external services.\u003C\u002Fp>\n","Add Saudi Arabia region and city choices to WooCommerce classic checkout without external services.",75,"2026-07-10T22:21:00.000Z",[45,59,60,61,62],"checkout","commerce","saudi-arabia","shipping","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Faetos-saudi-checkout-regions.1.0.0.zip",{"slug":65,"name":66,"version":38,"author":5,"author_profile":6,"description":67,"short_description":68,"active_installs":20,"downloaded":69,"rating":20,"num_ratings":20,"last_updated":70,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":71,"homepage":49,"download_link":75,"security_score":9,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"arabic-clean-permalinks","Arabic Clean Permalinks","\u003Cp>Arabic Clean Permalinks helps Arabic WordPress sites create readable Latin slugs from Arabic post and page titles.\u003C\u002Fp>\n\u003Cp>When a post or page is saved, the plugin can replace an empty or WordPress-generated Arabic slug with a clean Latin version. If a user has already edited the slug manually, the plugin leaves it unchanged.\u003C\u002Fp>\n\u003Cp>The plugin works locally inside WordPress. It does not call any external service, does not add front-end assets, and does not collect analytics.\u003C\u002Fp>\n\u003Cp>Built by the team behind Aetos SEO at NSR Elmtagr Digital Marketing.\u003C\u002Fp>\n\u003Cp>Main features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Arabic-to-Latin transliteration for post and page titles.\u003C\u002Fli>\n\u003Cli>Automatic slug generation only when the slug is empty or still appears generated from the title.\u003C\u002Fli>\n\u003Cli>Manual “regenerate clean slug” button in the post\u002Fpage editor.\u003C\u002Fli>\n\u003Cli>Settings for posts, pages, separator style, and WordPress old-slug redirects.\u003C\u002Fli>\n\u003Cli>Arabic and Persian digit support inside generated slugs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>Arabic Clean Permalinks does not collect personal data, does not track users, and does not send data to external services.\u003C\u002Fp>\n","Transliterate Arabic post and page titles into clean Latin WordPress slugs without overwriting manual permalinks.",90,"2026-06-28T22:09:00.000Z",[45,72,28,73,74],"permalinks","slugs","transliteration","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Farabic-clean-permalinks.1.0.0.zip"]