Release Notes

What we shipped

• When we lose access to a connected site, the notice now offers a direct route to delete that site and everything stored for it.
• Our terms spell out what we keep after access is lost, why we keep it, and how long copies stay in backups.
• If we can no longer reach your site, the delete confirmation says so, and tells you where to remove anything we put there yourself.

What it means for customers

Some platforms never tell us when an app has been removed. We only find out because our requests start being refused, and a refusal can just as easily be a temporary fault. So we do not delete your growth plan on a guess, and reconnecting brings you back to exactly what you had. What was missing was the other half: a clear statement of what we hold, and a direct route to say you want it gone. Both are there now, and the decision stays yours.

What we shipped

• When we set an improvement aside because your site was not ready for it, we now come back and check. If the reason has gone, the work goes back in the queue on its own.
• Some changes we made were live on your site all along, but we had checked too early to see them. We look again, and mark them done once they show up.
• A change we can see on your live page no longer asks you to publish it. That message only appears when something really is waiting for you.
• We watch the check itself, so if it ever stops running we hear about it rather than finding out weeks later.

What it means for customers

Until now, an improvement we could not apply on the day stayed set aside for good. On one site that meant ten pieces of work sitting untouched for seven weeks, including the pages it had been built around, while everything looked healthy from the outside. Nothing was lost, but nothing moved either. Now it moves.

What we shipped

• Lovable has its own option when you connect a site. Pick it, choose your repository, and we take it from there. The same works for Bolt and v0.
• We ask once whether we may give each of your pages its own title and description. Sites built this way start out sharing a single one across every page, and Google shows that same line for your pricing page as for your about page.
• Say yes and we make the change for you straight away. We add one small library to your project and give each page its own title and description, starting from the ones your site already has, then improve them one page at a time. It all goes in as a single commit, and if anything about your project does not look right to us we leave it alone rather than guess.
• Saying no is a real answer, not a dead end. We still improve your wording, write new pages, and keep your sitemap and robots file in order. What we leave alone is the titles and descriptions that show up in Google. You can change your mind later from site settings.
• If Lovable hosts your site, we tell you when changes are ready and waiting for you to click Publish, both on your dashboard and in your weekly email.
• If nothing gets published for a week, we pause instead of stacking up work you cannot see, and pick straight back up once you publish.

What it means for customers

A site built with an AI builder is easy to launch and hard to get found. This is the part that comes next. The one thing we are upfront about: Lovable only updates your live site when you click Publish inside it, and nobody outside can click that for you. If you would rather never think about it, connect your Lovable project to Netlify or Vercel and point your domain there. They rebuild on their own, and Scaup goes back to being completely hands-off. We work out which of the two you are on by ourselves.

What we shipped

• The image you pick for a new post is now set as the post's featured image, so your theme shows it where it belongs, and it appears on category pages and in link previews when the post is shared.
• Scaup checks the published page to see whether your theme already displays that image, and only places it in the article body if the theme showed nothing. No more of the same picture twice.
• A new switch under Advanced in your site settings, "Let your theme style new posts". Turn it on and we publish clean article HTML for your own design to handle, instead of adding our own spacing and width.
• Image descriptions are now written in your site's language rather than always in English.
• Your "About your business" notes now reach every step that writes text, so instructions about wording are followed, not just the choice of topics.
• A wider mix of work in your plan. No single kind of improvement can take over more than 40 percent of it, and issues that are not really about page titles are no longer turned into page-title items.

What it means for customers

Two of these came from customers who told us Scaup was stepping on their design. The styling switch is off to begin with, because the spacing we add is what makes posts look right on themes that style nothing at all. If you have built your own theme and want it to take over, turn the switch on and the next post will follow your design. All of this applies to new posts. Anything already published stays as it is.

What we shipped

• Before Scaup applies anything to a Webflow site, it checks whether you have edits sitting in the Designer that you have not published yet.
• If you do, we still make our changes, but we hold back the publish. Our work sits staged next to yours and goes live together the next time you publish.
• Your site page in Scaup shows a short note while a publish is held back, so you know why a change has not appeared on the site yet.
• Changes we held back are no longer counted as failures, so a page never gets skipped over work that applied correctly.

What it means for customers

Webflow publishes a whole site at once. There is no way to publish a single page, which meant that publishing one of our SEO changes would also push whatever you had left half finished in the Designer. Now it waits for you. You decide when your site goes live, and our changes ride along with your next publish.

What we shipped

• If your Wix site needs to approve a new version of the Scaup app, a banner now appears at the top of your site's dashboard explaining what to do and linking directly to the right place in Wix.
• A "Check again" button lets you clear the banner the moment you have approved the update, without waiting until the next day.
• A daily background check clears the banner on its own once the update is approved, so you do not have to come back to Scaup at all.

What it means for customers

Wix applies minor app updates for you automatically, but major ones need a quick tap in your own Wix dashboard. If yours needs it, the banner tells you exactly where to go and what to tap. Nothing breaks if you skip it for now; this unlocks an upcoming feature rather than fixing something that is broken.

What we shipped

• The picture chooser on the review screen used to show a small handful of your most recent images and nothing else.
• You can now search your images by name, and keep loading more until you find the one you want.
• It also shows more pictures at a time, so most people find the right one without searching at all.

What it means for customers

If the right picture was uploaded a year ago, you can still use it. No more settling for whatever happened to be recent, and no trip into WordPress to hunt the image down yourself.

What we shipped

• When you review a new blog post before it goes live, you can now pick which of your existing categories it should be filed under, right from the review screen.
• New posts that publish on their own go into your site's default category. Scaup no longer invents a brand new category for each post.
• If you have set a fixed category in settings, that is still used whenever you have not picked one.

What it means for customers

Your blog stays tidy. Posts land in the categories you already use instead of creating a long list of one-off categories over time, and you stay in control of where each post shows up.

What we shipped

• Plan generation now discovers pages from the sitemap, GSC, and internal links, raising the cap from 25 to 100 pages per site. Small sites get full coverage instead of exhausting their plan in one pass.
• For pages with multiple sections, Scaup now creates separate improvement items per section instead of one big change. Each edit targets a specific part of the page, making changes smaller and safer.
• A persistent page index stores the structure of every crawled page so monthly refreshes can skip pages that have not changed since the last crawl.

What it means for customers

Sites with fewer than 100 pages no longer idle for weeks after an initial plan. The system sees the whole site and spreads work across more pages. Edits are smaller and more targeted, which means fewer apply failures and a steadier stream of visible progress in the weekly email.

What we shipped

• Every week we check your site for the things that can quietly hurt your Google ranking: a malware or scam flag from Google, hidden spam links slipped onto your pages, and other signs your site was tampered with.
• If a serious problem shows up, we email you once with a plain-language explanation of what we found and what to do about it. No jargon, no dashboard to check.
• We only email you when a new problem appears, so you never get nagged week after week about the same thing.

What it means for customers

You do not have to remember to check anything. If your site gets hit with something that could drag down your Google ranking, we tell you straight away and in words that make sense. We are honest that some of these are things you or your web person need to clean up, not something we change for you automatically.

What we shipped

• WordPress site owners can now pick one category in settings, and every new blog post we write for you gets filed under it.
• Leave it on "Automatic" and we'll keep choosing the best fit for each post, just like before.

What it means for customers

If you keep your blog organized around a set category, your new posts land in the right place from the start, with nothing to move afterward.

What we shipped

• Site Protection now flags when your pages link out to spam sites (gambling, pills, adult, and the like), which usually means links were slipped onto your site without you knowing.
• It also spots cloaking, when a page shows Google something different from what real visitors see, a classic sign of a hacked site that Google penalizes hard.
• Both run on every platform and never touch your site. When something turns up, we show you the exact sites in plain text.

What it means for customers

Two of the sneakiest ways a hacked site quietly loses its Google ranking now get caught and explained in plain language, with nothing for you to set up.

What we shipped

• Each check on your Ranking protection card now has a small info icon. Hover or tap it and you get one plain sentence explaining what that check looks at, no jargon.
• The explainers read the same whether a check passed or flagged, so you always know what "Not flagged by Google", "No hidden junk", "No suspicious add-ons" and "Loads securely" actually mean.

What it means for customers

You no longer have to guess what the protection card is telling you. Every check explains itself in one sentence a non-technical person can follow.

What we shipped

• The site protection scan used to read only the regular text of your pages. It now also reads the content you built with Elementor, where some hidden spam links and injected code can hide out of sight.
• Anything suspicious found in an Elementor layout is reported the same way as before, including the actual hidden links so you can see exactly what was planted and get it removed.

What it means for customers

If your site is built with Elementor, the protection scan now looks in one more place attackers like to use. It's a wider net for the hidden junk that can quietly drag your Google ranking down, with nothing for you to set up.

What we shipped

• Site Protection now checks whether your site loads over a secure connection, the padlock you see in the browser address bar. It runs on every platform, not just WordPress.
• If a page loads insecurely, or a secure page still pulls in pieces over an insecure connection, we flag it in plain language and tell you what to ask your host to fix.

What it means for customers

Google favors secure sites and visitors leave when a browser shows a "Not secure" warning. This check makes sure a broken padlock isn't quietly costing you rank and sign-ups.

What we shipped

• When Scaup creates a new page to target a keyword gap, it now builds the page with a clean, readable design that renders well on any WordPress setup: custom themes, Gutenberg, Elementor, or WooCommerce. The page picks up your site's own fonts so it fits right in.
• No page builder and no template to pick. The same approach works whether your site is a plain theme or a heavily-built one, so new pages come out looking right the first time.
• In the review step, you get a live preview of the finished page and can choose the featured image from your own media library before it goes live.

What it means for customers

Before, a new page tried to copy the look of your existing pages, which could come out plain or mismatched on some sites. Now every new page gets a consistent, clean design that reads well anywhere, with a preview so you see exactly what will publish.

What we shipped

• New blog posts we write for Wix sites now publish with real headings, bullet lists, and bold text instead of one long wall of words. Each section gets its own heading, so the page is easy to skim on a phone.
• The formatting picks up your site's own blog styling, so a new post looks like it belongs on your site.
• We also added a quick readability check that flags any post that reads as a single unbroken block before it goes live.

What it means for customers

Readers stay on a page that's easy to scan, and Google rewards content that's well structured. Wix posts now match the quality of what we already publish on WordPress sites.

What we shipped

• The WordPress security scan now flags add-ons that register themselves with blank details, no version, no maker, no description. When a site gets hacked, attackers often hide a fake add-on with a harmless name like "WordPress Fix". Real add-ons always say who made them; the blank ones don't, and now we catch them.
• All of this reads details WordPress already keeps about installed add-ons. The scan stays read-only and never touches the site's files.

What it means for customers

A real customer's site turned out to have exactly this: a nameless add-on hiding behind the label "WordPress Fix". The scan surfaced it. It's the kind of thing that quietly tanks your Google rankings, and it's hard to notice by hand.

What we shipped

• Country-scoped keyword data. Search Console pulls, keyword filters, and competitor analysis are now scoped to the site's target country. A Bali hotel no longer sees noise from people searching in random other markets.
• Live SERP verification. The keyword positions shown in the report are checked against a real Google search from the customer's primary country, not just a 28-day GSC average that blends locations.
• Daily-or-weekly email frequency. Customers can now pick how often they want their recap email. Same content, customer's cadence. Setting lives in site settings, switchable any time.
• Auto-translated recap emails. If the site is in Spanish, Portuguese, French, Hebrew, etc., the email arrives in that language. Picked up from the site - nothing to configure.

What it means for customers

The rank numbers in the report now match what a real searcher in the customer's country would see, instead of a blended average that hides what's happening in the market they actually care about. Customers who want a daily nudge pick daily. Customers who want a clean weekly roll-up pick weekly. And the recap arrives in the site's own language, so a Brazilian customer isn't reading their progress report in English.

What we shipped

• The stats section no longer says "down from X last week" when impressions or clicks dip. Week-to-week swings on a small site are mostly noise, and showing them as losses is misleading. We now show the absolute number instead.
• Keyword wins are gated by a real signal floor. A keyword has to clear at least 5 impressions in the week to count as movement. One or two stray impressions can no longer surface as a "ranking improvement."
• Wins are also geo-filtered. A North-based business will no longer see a Jerusalem-only keyword bubble up as a win because somebody on holiday clicked it once.

What it means for customers

The weekly recap stops creating drama where there isn't any. No "you dropped 12%" when nothing actually changed, no "you're ranking for X" when X is a one-click ghost. What's in the report matches what's actually happening on the site. That's the only way it stays useful three months from now.

LinkedIn post (ready to copy)

Most SEO reports have a quiet design problem: they manufacture emotion.

A 6% impression dip on a small site is statistical noise. But the report says "down 6% from last week" and the founder spends Monday morning anxious. A keyword catches one stray click from someone in the wrong country, and the report says "you're now ranking for [keyword]" and the founder spends Monday morning excited about a number that will be gone next week.

Neither of those moments is real. Both of them erode trust over time, because eventually the founder figures it out.

This week at Scaup we shipped the unglamorous fix:

- We don't frame week-over-week as "down" when it's noise. Absolute number only.
- Keyword wins need a real signal floor before they show up. Single-impression flukes are filtered out.
- Wins are matched to the customer's country. A North-based business doesn't see a win from a city they don't serve.

The recap should match reality. If a real thing improved, say so. If nothing meaningful happened, say nothing happened. The reason people stop opening dashboards isn't that they're bored. It's that they stopped trusting the numbers.

What we shipped

• A substance gate. Before drafting a new page, the system checks for a real user question and concrete facts to use. If the raw material is too thin, we skip the page instead of publishing filler.
• A hard cap on related variations. We never produce more than a handful of pages per topic, and each has to use materially different facts (no swapping a city name and calling it a new page).
• Anti-AI-writing filters extended. Em dashes, "leverage," "seamless," rule-of-three sentences, and "ing-analysis" patterns are stripped before anything reaches a customer site.
• Every prompt now opens with a one-line standard: every page must be defensible under Google's helpful-content guidance.

What it means for customers

The most common worry we hear from founders building with AI tools is that Google will flag their AI-written pages and tank their rankings. The honest answer is that Google does not flag AI content for being AI. It flags content that doesn't help users. These changes make it structurally impossible for Scaup to produce the patterns Google does penalize, so customers can run the system without worrying about a policy hit.

Deep-dive article

LinkedIn post (ready to copy)

One of the most common questions I get from founders building with AI tools: "Will Google flag my site as AI content and tank my rankings?"

It's a fair worry. Here's what's actually true.

Google's policy (restated in their March 2024 spam update) doesn't target AI. It targets "scaled content abuse." Mass-produced thin pages. Near-duplicates with a swapped city or product name. Content that doesn't answer the search. Whether AI wrote it, you wrote it, or both, the rules are the same.

What actually hurts your rankings isn't who wrote the page. It's whether the page is useful.

That's the bar we hold ourselves to at Scaup. When the raw material isn't there to make a page genuinely useful for a real user, we publish nothing that day instead of filling space. That's harder to build than "always publish something," but it's the only honest way to run automated SEO.

The point isn't to avoid AI. The point is to never produce the pattern that gets sites demoted, by design.

Wrote up the full story (what Google actually penalizes, what to check on your own site, how we think about this): https://scaup.io/does-google-flag-ai-content