Auto Installed Without My Consent

  • Ravenous Raven Design

    (@ravenousravendesign)


    1 week, 6 days ago

    I want to formally express my concern regarding the automatic installation of AI-related website builder tools on client websites without explicit approval or opt-in consent.

    As someone who manages and maintains client websites professionally, I strongly oppose the idea of AI tools being injected into production environments by default, especially on established business websites that rely on stability, SEO integrity, and carefully managed design systems.

    My concern is not about AI itself. I use AI strategically in controlled workflows where appropriate. My concern is specifically about hosting providers automatically installing tools that can potentially modify content, generate pages, alter layouts, or interfere with existing site architecture without the informed approval of the agency or site owner responsible for maintaining the website.

    Many of these AI tools generate low-quality “AI sludge” content that can damage SEO quality, create semantic duplication, produce inaccurate business information, and flood websites with thin or poorly structured pages. For agencies and businesses that have spent years building authority, rankings, and conversion-focused content, this introduces unnecessary risk.

    Additionally, many AI builders are primarily designed around Gutenberg or generic WordPress structures and are not deeply integrated with proprietary ecosystems like Divi. This creates potential compatibility issues, layout instability, builder conflicts, and workflow disruption on custom-built sites.

    There are also legitimate concerns about security, permissions, and operational control. Any plugin capable of generating or modifying content at scale should never be introduced automatically into client environments without explicit authorization. Clients may unknowingly experiment with these tools and unintentionally damage carefully planned SEO structures, branding consistency, or conversion-focused layouts.

    Professional websites are not experimental sandboxes. Many agencies manage live business environments where downtime, layout corruption, index bloat, or poor AI-generated content can directly impact leads and revenue.

    At minimum, these tools should require:

    • explicit opt-in approval,
    • transparent disclosure,
    • easy removal,
    • and clear documentation regarding exactly what access and modifications they are capable of making.

    I believe hosting providers should prioritize stability, transparency, and professional control over aggressively pushing AI tooling into environments where it may not be wanted or appropriate.

Viewing 1 replies (of 1 total)
  • Daniela Ivanova

    (@daniellaivanova)

    1 week, 5 days ago

    Hello @ravenousravendesign,

    To provide some context on our side, the core framework of the recent WordPress 7.0 major release introduced native, underlying AI infrastructure capabilities. In anticipation of this update, we deployed our AI Agent plugin as a seamless, ready-made connector designed to bridge the gap between WordPress core and our SiteGround AI Studio service out of the box

    However, we want to completely reassure you on the points of risk and control you mentioned:

    The AI Agent plugin acts strictly as an available interface and connector. It does not possess autonomy to generate sludge content, modify your established design frameworks, inject pages, or alter layouts automatically. It remains completely dormant unless actively engaged by a user.

    We fully agree that professional websites are not experimental sandboxes. Because of this, the plugin is entirely non-mandatory. You have complete control to deactivate and permanently delete the plugin from the WordPress dashboard on any or all of your client sites, which immediately cuts the connection to the AI Studio infrastructure.

    We value your insight regarding complex, proprietary ecosystems like Divi.

    Also, thank you for your feedback regarding the necessity of a strict “opt-in” model, rather than an “opt-out” rollout for agency and production environments.

    I will pass your notes directly to our core plugin development team and product management. Feedback from technical professionals who manage extensive portfolios is a valuable asset.

    Best Regards,
    Daniela Ivanova

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.