ShardStitchGet ShardStitch ShardDesign
Build with your AI. Edit it yourself.
A visual workspace for the website you already built. We're developing ShardDesign so you can change text, replace photos, adjust spacing and refine layouts inside ShardStitch, with changes saved to your own project files.
Also planned: a Guardrails MCP for founders preparing to publish and owners of AI-built websites already losing search visibility. It is intended to give your AI coding tool a sitewide evidence review and a prioritized repair scope, alongside visual editing.
From AI-built to personally edited
Start with your own files
Import a local website project created with an AI coding tool or by a developer. Compatibility depends on its framework and source structure.
Edit on the page
The planned experience combines direct selection, a properties panel, image tools and layout controls. Routine manual edits should not require an AI request.
Keep your source and your choices
Review changes, undo mistakes and keep working on the same files with your AI tool. Publishing from the workspace is part of the roadmap.
Built so far, in development
Internal builds have demonstrated these workflows on a disposable React/Vinext storefront project:
- Edit static text and mixed headings while preserving their structure.
- Change typography, spacing, borders and other supported Tailwind styles.
- Choose project images, reorder sibling sections and preview different screen sizes.
- Edit supported catalogue records, including product names, images and prices.
- Review source differences, undo changes and restore checkpoints.
What we're working toward
- A consistent workspace for supported HTML and React projects.
- An add-element toolbar and visual resize handles.
- Clearer placement, alignment and responsive editing controls.
- Broader testing on independently created websites.
- A verified preview-and-publish workflow.
Development status: 8 September 2026. ShardDesign is not publicly released. Direct canvas gestures need re-verification in the newest workspace build; one successful project is not universal compatibility.
Compatibility comes before promises
| Website type | Current development status |
|---|---|
| React + Vite | Editing demonstrated on a controlled test project. Broader import testing is pending. |
| Vinext | Content, style and catalogue workflows demonstrated on a disposable SonicTrigger project. |
| Plain HTML / CSS | An existing editor is in development; unifying its interface with the new workspace is planned. |
| Next.js, Vue, Svelte, Angular | No native support is being announced at this stage. |
A website made with Claude, Codex, Cursor, Gemini, Lovable, Bolt or v0 is not automatically compatible. We will publish tested support and limitations before release.
Guardrails MCP: scope the whole site, not just one page
A website can look finished while its pages repeat the same answers, cite unrelated documentation or promise more than the product supports. The planned ShardDesign Guardrails MCP will help your connected AI assistant inspect those patterns across a sitemap or supported project, return the affected URLs and evidence, and propose an ordered repair plan for your approval.
Scaled content and duplicate-page risks
Google's scaled content abuse policy concerns large amounts of content produced primarily to manipulate rankings without helping users, whether written by people or AI. A repeated layout alone does not establish abuse. The proposed checks focus on repeated main-content passages, interchangeable answers and missing page-specific value, not shared navigation or a word-count target.
Doorway candidates, with the differences preserved
Doorway abuse includes substantially similar pages aimed at related queries that funnel visitors toward a more useful destination. The MCP is intended to map each page's purpose and identify overlaps for review. A recommendation might be to strengthen a distinct answer, carry valuable material into a better destination, or leave a useful specialist page intact. A similarity score will not automatically trigger a redirect.
Evidence and technical checks together
- Compare FAQ answers, closing claims and recovery instructions across pages, with excerpts showing what overlaps.
- Review citation relevance, broken links, changed source content and dated verification claims. A reachable link is not proof that it supports the claim.
- Check hub-versus-detail feature claims, canonicals, redirects, sitemap entries and metadata consistency.
- Map review findings to Google Search Central guidance and Bing Webmaster Guidelines, with source dates and uncertainty shown.
From review to an agent-ready repair scope
The intended workflow starts with your sitemap or supported project. Add authorized Search Console and Bing data when available to distinguish content concerns from observed search performance.
Review affected URLs, exact evidence, confidence and proposed fixes with your AI tool. Preserve useful content and existing winners before approving edits, consolidation or any URL change.
Use ShardDesign's planned original/draft review for supported edits, check the changed pages, then compare complete before/after performance windows. Traffic-drop alerting is a later planned extension, not an available feature.
The Guardrails MCP is not publicly available. This is a planned Shard product-family feature, not an internal deployment gate, a Google/Bing endorsement or universal support for every website. It will not automatically publish repairs or remove pages.
Spam updates: policy context, not a diagnosis
Google's September 2026 spam update began on September 24, according to its official status dashboard. That announcement does not identify a particular site's cause of decline or say that this rollout specifically targets duplicate pages.
The planned MCP will surface official Google and Bing guidance alongside dated update context. Search Engine Roundtable's update reporting will remain separately labeled third-party commentary, not official confirmation.
The goal is to help users remove verifiable weaknesses before publishing and scope useful repairs when search visibility falls. Review findings identify potential problems; they do not establish the cause of a ranking change.
Policy context checked September 27, 2026. Google's spam-update guidance says compliant changes may take months to be recognized. Better content and technical fixes can support a recovery effort, but ShardDesign cannot guarantee regained impressions, clicks, rankings or protection from future updates.
Before you plan around it
When can I use ShardDesign?
There is no public release date yet. This page announces work in progress. Release availability and supported workflows will be recorded in the changelog.
Does it replace ShardStitch recovery?
No. ShardDesign is an addition to ShardStitch. Recovery and context continuity remain part of the product, and the design workspace is intended to help you maintain what you build.
Can Guardrails MCP tell me why Google traffic fell?
It is intended to identify evidence-backed risks and help you scope repairs, not expose Google's internal ranking decisions. Similarity, missing citations or an update date are not proof of a penalty. Authorized performance data can help measure changes; a recovery timeline or increase in clicks cannot be promised.
Can it edit any AI-built website?
Not yet. Compatibility depends on the project's framework and source structure, not which AI tool generated it. Editing has been demonstrated on a controlled React/Vinext project; broader import testing and a supported-framework list are still in development.
Is it included in the current purchase?
This announcement does not change the current licence or promise a release bundle. ShardDesign's availability and packaging will be confirmed before launch. Buy the current product for the capabilities available today.
What would you like to edit?
Tell us which tool built your website and the changes you want to make: a photo, a layout, a product catalogue or something else. That helps us choose realistic projects for compatibility testing. Please do not send passwords, customer records or private source code.
Contact the ShardStitch team →