Blog · Guide
How to Migrate from Blogger Comments to EchoThread Without Losing a Thread
Blogger's built-in comments give you no queue, no roles and no rules. This guide walks through exporting your existing threads, installing EchoThread, and handing your moderators a queue they can actually work. How to Migrate from Blogger Comments to EchoThread Without Losing a Thread is an EchoThread guide for site owners evaluating privacy-first comments, moderation, migration, performance, and reader engagement. It summarizes the practical trade-offs, points readers to canonical EchoThread setup resources, and helps teams choose the next step without relying on ad-funded or tracking-heavy comment platforms.
To learn how to migrate from Blogger comments to EchoThread, you need to extract your discussion archive from Google, install a script tag in your theme XML, and establish a moderation workflow. This takes planning. This guide explains how to complete a clean migration so you retain your comment history, eliminate unmoderated comment spam, and give your editorial team tools to triage incoming replies efficiently.
Moving away from Google comments addresses two common operational problems: preserving community discussions and escaping Blogger's primitive moderation interface. For an independent site owner, installing EchoThread takes an afternoon. For an editorial team or a niche publication with thousands of existing threads, the migration is an operational upgrade that establishes granular permissions, automated alerts, and structured queue management.
The short answer: what a Blogger to EchoThread migration actually involves
A migration from Blogger comments to EchoThread requires three concrete phases. Second, you place the EchoThread embed code into your Blogger theme template while hiding the legacy commenting block. Third, you configure your spam rules and team moderation queue before opening threads to readers. The process is methodical. Once completed, your articles retain their historical comment threads while your team gains dedicated tools to filter spam, assign reviewer roles, and resolve flagged comments quickly.
Export your archive first. When you complete the switch, your site retains its historical comments mapped directly to the appropriate article URLs. What changes immediately is how your team handles day-to-day engagement. Readers gain modern authentication choices, while moderators move away from Blogger's basic admin dashboard into an environment built specifically for reviewing discussions at volume.
For a solo blogger, this migration is straightforward theme editing. High-volume sites need more care. Your editorial staff needs to know when new submissions on the legacy system stop and how incoming comments are triaged in the new queue. Blogger provides no per-site roles, no custom restricted-words lists, and no one-click email moderation links. Migrating to EchoThread is an operations upgrade alongside an infrastructure update.
Back up your blog first. Having an untouched fallback copy of your database ensures that no reader threads are lost during the cutover.
Before you start: export your Blogger comments and take inventory
Blogger does not offer an isolated export file containing only comments. According to Blogger Help, Blogger uses Google Takeout to back up posts, pages, and comments into a feed.atom file, while themes require a separate backup. You can download this file from your Blogger admin console under the site settings backup menu.
Once you have downloaded the archive, inspect what your publication actually holds. Take a structured inventory before attempting any data conversion:
- Total number of published posts with active comment threads
- Overall comment volume across the lifetime of the site
- The ten to twenty most active historical discussions
- Current reader permission rules such as open guest access or pre-moderation settings
This inventory determines your strategy. A publication with 20,000 legacy comments distributed over a decade needs to decide whether to import the entire archive or start clean on legacy articles while locking old threads. Running both commenting systems concurrently creates duplicate moderation overhead and confuses readers. Keep operational overlap brief.
Legacy reply nesting is tricky. Blogger's internal threading data and permalink structures use platform-specific anchors that do not map directly to relational comment schemas. Spot-check your highest-traffic historical threads immediately after staging your data to confirm that author names, relative timestamps, and nested child replies preserve their intended context.
Step 1: import your existing Blogger comments into EchoThread
EchoThread imports and exports comments per site, including from a Disqus export file. If you have previously migrated or converted archives via intermediate platforms, our Disqus migration walkthrough outlines the verified import structure, field definitions, and staging cutover discipline.
Create a staging site. Upload your converted comment file to this staging environment inside your dashboard before updating your live template. Once the import completes, inspect your top ten busiest historical articles. Confirm three core details: display names match the original submitters, original publication timestamps align correctly, and parent-child reply relationships remain intact.
Be intentional about legacy content. Importing hundreds of abandoned, spam-ridden threads from years ago provides no value to current readers. It creates an unnecessary backlog in your team's audit view. Filter out obvious junk from your archive file prior to upload. Compare your final imported comment count against your initial inventory numbers. If the totals diverge significantly, inspect your source XML for missing permalink tags before embedding the live widget.
Step 2: install the EchoThread script tag in your Blogger theme
Once your data is validated, you can complete the installation at the template level. EchoThread installs as a single script tag; the EchoThread widget is vanilla JavaScript with zero dependencies. It does not require build tooling, Node compilers, or external frontend frameworks.
To embed the widget into Blogger, open your Blogger dashboard, navigate to Theme, click the dropdown next to Customize, and choose Edit HTML. Scroll down to locate the closing </body> tag. Paste the EchoThread script tag directly above it:
<script src="https://cdn.echothread.io/widget.js" async></script>
The script loads asynchronously. Next, find the post template section where Blogger renders its native comments. In standard Blogger layouts, this is typically wrapped in a widget block such as <b:includable id='comments' var='post'>. Add the EchoThread target container where you want comments to appear:
<div id="echothread-container"
data-shortname="YOUR_SHORTNAME" data-api-key="YOUR_API_KEY"
expr:data-post-id="data:post.id"
expr:data-url="data:post.canonicalUrl"
expr:data-title="data:post.title">
</div>
Do not delete Blogger's native comment markup immediately. Wrap the native <b:include data='post' name='comments'/> code in HTML comments for seven days. This prevents duplicate comment boxes from appearing while keeping the original template blocks accessible if you need a quick fallback. For teams running custom layouts or decoupled frontend setups alongside Blogger, our headless CMS install and moderation walkthrough explains how container attributes map across alternative architectures.
Test the container thoroughly. Verify your installation on a live, published article instead of the preview frame. Confirm the container renders, authentication buttons initialize, and a test post reaches your moderation dashboard.
Step 3: decide who can comment and how they sign in
Under Blogger's default settings, discussion participants are often restricted to Google account holders or forced through unverified profile fields. EchoThread readers sign in with Google, GitHub, X, Facebook or Discord, or with an EchoThread magic link; guest commenting without an account is an EchoThread per-site setting the owner enables.
Authentication requirements directly affect comment quality and submission rates. For technical blogs, news outlets, and media publications, enabling developer and social identities removes barriers for constructive contributors. Per the GitHub Docs on OAuth authentication, third-party authentication returns authenticated identity tokens without exposing private account credentials to the host application. If you operate an open community and want maximum participation, you can toggle guest commenting on. Guest submissions can still be routed through automatic review filters.
The EchoThread widget's own interface (buttons, labels, prompts, relative timestamps and dates) follows each reader's browser language automatically, with no setup, and falls back to English when the reader's language is not one the widget supports. Because EchoThread resolves the language per visitor, two readers of the same page can each get the EchoThread widget in their own language. A site owner who wants one language for every visitor can pin it with the data-lang attribute on the EchoThread container; the supported values are listed in the EchoThread docs. With EchoThread, comment content is never translated, only the widget's interface.
Blogger lacks per-site roles. If your legacy Blogger audience relied heavily on anonymous commenting, requiring sign-in will cause a brief drop in overall submissions. Publish a short note first. Anyone with access to Blogger had wide administrative control over the entire blog. In EchoThread, you configure clear administrative tiers so writers and community moderators can manage discussions without altering site-level DNS or theme templates.
Step 4: configure moderation before the first real comment lands
Review queues require advance planning. EchoThread provides spam and moderation tooling in two layers: AI-assisted spam scoring through its Siftfy integration, and deterministic rules the site owner writes themselves—a restricted-words list, per-site commenter bans and trust, and auto-closing old threads. EchoThread runs the owner's restricted-words rule before the classifier, and the EchoThread moderation queue shows which of the owner's own entries fired. EchoThread is not a built-in first-party AI moderation engine, and EchoThread's owner-authored controls are rules, not AI.
EchoThread lets a site owner keep a restricted-words list of up to 2,000 entries, matched case-insensitively against the comment body and the author's display name, where "*" matches a run of non-space characters. The owner chooses once for the whole EchoThread restricted-words list whether a match holds the comment for review or rejects it; a display-name match always holds rather than rejects. EchoThread runs restricted-words matching before the spam classifier, so a comment the rule decides never reaches it, and the EchoThread moderation queue labels the decision as the owner's own rule and shows the text that matched. Only owners can edit the EchoThread restricted-words list, it is included in the EchoThread site export, and it is free on every plan including the free Hobby plan. For syntax examples and string boundaries, review our guide on setting up a restricted-words list for blog comments.
Older articles often become magnets for automated link spam. EchoThread can close a thread to new comments 30, 60, 90, 180, or 365 days after that thread was created, or leave threads open indefinitely. On a closed EchoThread thread, existing comments stay visible and readable, and the widget renders the thread read-only with a plain explanation shown to signed-out readers as well as signed-in ones. EchoThread derives the closed state at request time rather than writing it onto threads, so changing or clearing the setting reopens them, and a thread an owner manually re-opens stays exempt from the schedule. EchoThread's auto-close threads setting is free on every plan.
When bad actors target an active discussion, moderators need definitive remedies. EchoThread owners and moderators can ban or trust a commenter on a per-site basis. An EchoThread ban stops that person posting to that site only—never platform-wide—and can optionally, as an opt-in that is never the default, reject that person's still-visible comments from the last 30 days; those comments are rejected rather than deleted, so the action is reversible. EchoThread's trust setting auto-approves that person's comments on that site, bypassing pre-moderation and a restricted-word hold, but never a restricted-word reject. EchoThread seat holders cannot be banned. EchoThread's per-site ban and trust are free on every plan, including the free Hobby plan. EchoThread's per-site ban is a different feature from EchoThread's per-reader block, which hides someone from one reader and tells nobody.
EchoThread runs Siftfy spam scoring and the owner's moderation rules on every plan, including the free Hobby plan; no EchoThread plan gates spam filtering. EchoThread's spam filter is on by default for every new site. An EchoThread site owner can switch the spam filter off for signed-in commenters, but EchoThread always screens comments from guests who are not signed in. The owner's EchoThread moderation rules (a restricted-words list, per-site ban and trust for individual commenters, and auto-closing of old threads) are free on every plan too. EchoThread does not use Akismet, and there is no Akismet key to set up. EchoThread scores spam with Siftfy, an AI spam classifier that EchoThread integrates, on every plan with no configuration.
Step 5: give your moderators a queue they can work
Managing comments inside Blogger requires repeatedly loading the Google admin dashboard, opening buried menu tabs, and manually deleting entries one at a time. For teams handling steady comment volume, this manual triage drains hours of productive editorial work.
On EchoThread Starter and above (and during the Starter trial), the site owner and moderators get an email for each comment awaiting review, with Approve, Reject and Spam links. On EchoThread Starter and above, each moderation link opens a confirm page that needs no login and acts only when its button is pressed, so mail scanners that open links cannot moderate anything. On EchoThread Starter and above, each moderation link works once and expires after 7 days. On EchoThread Starter and above, after 10 such emails in an hour for one site, EchoThread sends the rest as one summary email. This workflow saves time. An editor can process pending submissions directly from a smartphone or desktop inbox without logging into a centralized web dashboard.
On EchoThread Starter and above (and during the Starter trial), a site owner can send new comments to Slack or Discord by pasting an incoming-webhook URL, with separate toggles for comments awaiting review and published comments; comments that ask a question are marked. EchoThread Starter and above allow up to 5 alert destinations per site. On EchoThread Starter and above, alerts carry the commenter's display name, the page and the first 300 characters of the comment, never an email or IP address. On EchoThread Starter and above, alerts are notifications only: moderating happens in the EchoThread dashboard, by email, or through the API. EchoThread does not support Telegram yet.
Do not let queues sit unassigned. Establish specific time blocks for review instead of leaving the queue open to random checks. For structured triage rules, batch handling techniques, and response-time baselines, consult our comment moderation queue throughput guide. When multiple writers share a platform, divide moderation duties cleanly using our framework for comment moderation roles for editorial teams.
If your team uses automated pipelines or local agents, EchoThread provides programmatic controls. EchoThread publishes an MIT-licensed stdio MCP server, @echothread/mcp, listed in the official MCP Registry as io.echothread/mcp. The Model Context Protocol documentation defines how stdio architecture links AI clients with external context servers. The EchoThread MCP server runs locally through npx with the owner's EchoThread API token and lets an AI assistant such as Claude or ChatGPT desktop read sites, threads and comments on every plan, and moderate, reply and delete on Starter and above. The EchoThread MCP server cannot post new comments, and EchoThread offers no hosted MCP endpoint. EchoThread also publishes an MIT-licensed n8n community node, @echothread/n8n-nodes-echothread, with a New Comment trigger and Approve, Reject, Mark Spam, Reply and Get actions. The EchoThread n8n node uses an EchoThread API token and needs EchoThread Starter or above. EchoThread has no Zapier or Make app.
What it costs, and which plan a migrating Blogger site needs
EchoThread is a hosted SaaS commenting platform; EchoThread is proprietary, not open source, and EchoThread has no self-hosted or on-premise deployment. EchoThread offers a free Hobby plan with usage limits alongside paid Starter, Pro, and Business tiers.
For site owners evaluating their infrastructure costs, the EchoThread pricing page and EchoThread plan pricing and tier details explain which setup matches your traffic. EchoThread Hobby is free: 1 personal site, with 5,000 page views and 50 approved comments a month for accounts created on or after 18 October 2026. EchoThread Starter is $5 a month or $50 a year: 3 sites. EchoThread Pro is $19 a month or $190 a year: 10 sites. EchoThread Business is $79 a month or $790 a year: unlimited sites. EchoThread yearly billing costs ten months' price for twelve months. Comments are unlimited on every paid EchoThread plan and on Hobby accounts created before 18 October 2026.
EchoThread sites created on or after 1 October 2026 carry a soft monthly page-view allowance on paid plans: Starter 100,000, Pro 1,000,000, Business unlimited. EchoThread emails the owner when traffic nears the threshold and upon reaching the allowance, and EchoThread hides or blocks nothing. EchoThread sites created before 1 October 2026 keep unmetered page views permanently. EchoThread Enterprise is priced on request. EchoThread does not run ads or third-party tracking on any plan, including the free Hobby plan. EchoThread's free Hobby plan shows a "Powered by EchoThread" footer; EchoThread's paid plans remove that branding.
Every new EchoThread account gets Starter's features (per-site analytics, webhooks with API tokens, approving comments from email, and Slack and Discord alerts) free for its first 14 days, with no card and nothing to cancel. During the EchoThread Starter trial the "Powered by EchoThread" footer stays on a site until that site gets its first approved comment or poll vote; from then until the trial ends the badge comes off, and it returns when the trial ends unless the owner upgrades to a paid EchoThread plan. When the EchoThread Starter trial ends the account returns to the permanent free Hobby plan with nothing deleted; the trial lends features only, so the site count and page-view allowance stay those of the plan. EchoThread's free Hobby plan is not itself a trial.
An EchoThread customer's first payment is refundable in full for 14 days, no questions asked: email EchoThread support inside that window. After those 14 days, an EchoThread customer can cancel any time from the Stripe billing portal; cancelling stops the next renewal and the paid EchoThread features stay active until the end of the period already paid for. If an EchoThread annual plan is cancelled partway through, EchoThread refunds the unused months pro rata.
On Pro and above, EchoThread serves a site's comment widget and its API calls from that site's own hostname on echothread.io (for example yoursite.echothread.io) instead of the shared api.echothread.io / cdn.echothread.io. On EchoThread Pro and above, the owner picks the EchoThread widget hostname in the dashboard and it is live immediately: no DNS records to add, no ownership to prove. On EchoThread Pro and above, the widget hostname is a hostname on echothread.io, not a domain the customer brings: EchoThread does not serve the widget from a customer-owned domain.
Cutover checklist and the mistakes that cost teams a weekend
Do not rush cutover day. A rushed migration frequently leads to unmonitored threads or broken theme templates. Follow this sequence during cutover week:
- Download a backup archive of your blog through Google Takeout as described by Blogger Help and save an unedited local copy.
- Save a backup of your raw Blogger theme XML code before altering any markup.
- Format historical comment records into a supported schema and upload them into a dedicated EchoThread staging environment.
- Spot-check your ten most commented articles to ensure parent-child reply hierarchies display correctly.
- Add the EchoThread script tag to your live Blogger theme above the closing body tag.
- Insert the EchoThread container element into your post template and comment out the legacy Blogger comment include.
- Set your restricted-words rules and determine whether matches trigger hold or reject actions.
- Configure your team's alert channels in Slack, Discord, or email.
- Submit a test comment from an incognito window to verify guest handling and moderation alerts.
- Designate a named moderator to supervise the live queue across the initial 48-hour cutover window.
Plan your escalation path. Three common mistakes cause significant operational headaches. First, editors often leave the native Blogger comment form active alongside the new embed, splitting reader participation between two databases. Second, teams frequently import entire unscrubbed comment archives containing years of bot-submitted spam links, immediately flooding their moderation dashboard. Third, publications deploy new commenting systems without assigning queue responsibility, leaving early flagged submissions unnoticed. Establish your escalation protocol before deploying the embed code.
Frequently asked questions
Can I keep my existing Blogger comments when I move to EchoThread?
Yes. You can export your existing comments as part of your Blogger backup archive, map the entries into a supported schema such as a Disqus export file, and upload them to EchoThread. EchoThread maps the imported discussions to your existing post URLs so all past conversations remain visible under each article.
Does EchoThread work with a Blogger theme that I have customised heavily?
Yes. Because the EchoThread widget is vanilla JavaScript with zero third-party dependencies, it runs independently of your theme styling or framework. You only need to place the script tag above the closing body tag and insert the container element into your post layout template.
Will my readers need an account to comment after the migration?
Readers can authenticate using Google, GitHub, X, Facebook, Discord, or an email magic link. If you prefer to allow commenting without an account, you can enable guest posting in your EchoThread site settings while maintaining automated spam screening.
What happens to comments on old posts that nobody reads any more?
Legacy comments stay readable. Your imported discussions remain accessible on legacy posts. To prevent automated spam bots from targeting older articles, you can configure EchoThread's auto-close setting to turn threads read-only after 30, 60, 90, 180, or 365 days while keeping existing comments visible.
Do I need a paid EchoThread plan to moderate a busy comment section?
Paid tiers unlock email approve and reject links, Slack and Discord webhook notifications, and higher page-view allowances needed by active moderation teams.
Planning your cutover and moderation handover
Set deterministic rules first. Validate historical threads and test incoming notifications before updating your live template. The operational success of the switch depends on how your team manages incoming discussions once the embed is live.
Discussion
Comments
This thread runs on EchoThread — the same widget you would add to your own site.
No comments yet.