DEV Community: Anders Dahl Rasmussen

Etsy SEO in 2026: The Title Formula That Actually Ranks

Anders Dahl Rasmussen — Thu, 02 Jul 2026 05:19:01 +0000

Etsy SEO in 2026: The Title Formula That Actually Ranks

Etsy's algorithm has changed significantly. Here's what's working now — and what's killing your rankings.

The Core Problem with Most Etsy Titles

Most sellers write titles from a maker's perspective:

"Handmade Ceramic Mug"

Buyers don't search "handmade ceramic mug." They search:

"birthday gift for coffee lover" or "minimalist coffee mug white" or "ceramic pour over gift set"

The gap between how you describe your product and how buyers actually search for it is where most Etsy sellers lose traffic.

The 2026 Title Formula

Structure: [Primary Keyword] | [Secondary Keyword] + [Use Case] | [Material/Style]

Example for a ceramic mug:

"Coffee Mug Gift | Minimalist Stoneware 12oz | Ceramic Birthday Gift for Her"

What this does:

Leads with the buyer intent keyword (gift)
Includes size/material for filtering
Targets a specific occasion

Tags: The Most Underused Asset

You have 13 tags. Most sellers use 8-10. Using all 13 is a direct ranking signal — each unused tag is a missed search opportunity.

Tags should be phrases buyers search, not descriptors of your product. Think: "graduation gift under 30" not "blue ceramic."

The Fast Fix: ContentBase

Paste your current listing. Select Etsy. Get an optimized title, description, and all 13 tags in 10 seconds. Free, no signup, 5/day.

ContentBase is part of BaseAI Tools.`,

The Content Repurposing System That Saves 4 Hours Per Week

Anders Dahl Rasmussen — Thu, 02 Jul 2026 05:18:28 +0000

The Content Repurposing System That Saves 4 Hours Per Week

Most content creators are doing this wrong. They create content for one platform, then try to adapt it to others manually.

That's not repurposing. That's rewriting.

The Core Problem

Every platform has different expectations:

LinkedIn rewards depth and professional framing
Twitter rewards brevity and hooks
Instagram rewards visual-first storytelling
Newsletters reward intimacy and behind-the-scenes

The same idea needs different packaging for each. Doing that manually for every piece of content adds up fast.

What a Real Repurposing System Looks Like

Step 1: Create one canonical piece
Write the full version once — whether that's a blog post, YouTube script, or podcast outline.

Step 2: Extract the core insight
In one sentence: what's the main point? This becomes the anchor for all platform versions.

Step 3: Adapt, don't translate
Each platform version should feel native — not like a copy-paste from somewhere else.

The Math

If you have 3 content platforms and create 2 pieces per week:

Manual repurposing: ~90 minutes per piece × 2 = 3 hours/week
With a repurposing system: ~20 minutes per piece × 2 = 40 minutes/week

That's 2+ hours back per week, every week.

The Automation Option: RepurposeAI

Paste any piece of content. Select which platforms you need it for. Get ready-to-post versions in seconds.

Free for 3 repurposes per day. No account required.

RepurposeAI is part of BaseAI Tools.`,

Why Freelance Developers Lose Projects They Should Win

Anders Dahl Rasmussen — Thu, 02 Jul 2026 05:17:56 +0000

Why Freelance Developers Lose Projects They Should Win

The client posts a job. You're qualified. You write a proposal. You don't hear back.

This is the most common frustration in freelance development — and it has almost nothing to do with your skills.

The Proposal Problem

Most developer proposals look the same:

Brief intro ("I'm a full-stack developer with 5 years experience...")
Tech stack list
Rough timeline
Rate
"Looking forward to hearing from you"

The client reads dozens of these. They all blur together.

What Actually Gets You Hired

Winning proposals do something different: they make the client feel understood before making any promises.

The structure that works:

1. Demonstrate you read the brief
Quote their specific problem back to them. Not the job title — the actual problem they described.

2. Show you've solved this before
One specific example is worth more than a list of technologies.

3. Outline your approach
Not a timeline — an approach. How are you going to think about this? What questions would you ask on day one?

4. Make a specific ask
"Would you be available for a 20-minute call Thursday or Friday?" beats "looking forward to hearing from you" every time.

The Speed Problem

The first credible proposal often wins. Clients are making decisions in real time — they message multiple candidates and go with whoever seems competent first.

Writing a good proposal takes 20-45 minutes if you do it right. That's why most developers write generic ones.

The Solution: ProposalAI

Paste the job posting. Get a full, personalized proposal in 30 seconds. Edit as needed — the structure and personalization are already there. Free for 3/day, no signup.

ProposalAI is part of BaseAI Tools.`,

Why Your Airbnb Listing Gets Views But No Bookings (And How to Fix It)

Anders Dahl Rasmussen — Thu, 02 Jul 2026 05:17:04 +0000

Why Your Airbnb Listing Gets Views But No Bookings (And How to Fix It)

You have a great property. Photos are decent. Price is competitive. But the bookings aren't coming.

The problem is almost always the same: your listing copy isn't converting.

The Two-Second Rule

Guests spend an average of 2.4 seconds on a listing before deciding to click or scroll past. In those 2.4 seconds, they see your title and the first 150 characters of your description.

Most hosts write titles like:

"Cozy 1BR apartment in city center"

Top-performing hosts write:

"Sunlit Writer's Retreat · Steps from Market | Fast WiFi + Rooftop"

The difference isn't the property — it's the framing.

What Airbnb's Algorithm Actually Rewards

Airbnb ranks listings based on:

Booking conversion rate — what % of viewers book
Click-through rate — what % click after seeing your thumbnail+title in search
Response rate — how quickly you respond to inquiries
Review score — average rating

You control factors 1, 2, and 3 directly through your listing copy.

The Title Formula That Works

Structure: [Experience/Vibe] + [Standout Feature] | [Location Benefit] + [Key Amenity]

Examples:

"Modern Loft · City Skyline Views | 10min Metro + Dedicated WFH Space"
"Quiet Garden Cottage | Walk to Beach + Full Kitchen"

Description: Experience First, Amenities Second

Most listings lead with: "2 bedrooms, 1 bathroom, fully equipped kitchen..."

Guests already know the room count from the search filters. Lead with the experience:

"Wake up to mountain views and spend your mornings on the private terrace before heading into town — everything is 8 minutes away on foot."

Then cover the practical details.

The Fix: HostAI

Paste your current title and description. Select your platform (Airbnb, Booking.com, or Vrbo). Get a rewritten version in 30 seconds. Free, no signup.

HostAI is part of the BaseAI Tools suite.`,

How to Respond to Negative Google Reviews: A Complete 2026 Guide

Anders Dahl Rasmussen — Thu, 02 Jul 2026 05:16:54 +0000

How to Respond to Negative Google Reviews: A Complete 2026 Guide

Negative reviews happen to every restaurant. How you respond determines whether they hurt you or help you.

Why Your Response Matters More Than the Review

94% of diners check reviews before choosing a restaurant. But here's what most owners miss: they also read the responses.

A thoughtful, professional response to a 1-star review does three things:

Shows potential customers you care about service quality
Demonstrates you handle problems professionally
Signals to Google that you're an engaged business owner

The Anatomy of a Good Response

What to include:

Acknowledge the specific complaint (not generic "sorry you felt that way")
Take responsibility where appropriate
Offer a concrete next step (call us, come back, speak with manager)
Keep it under 200 words

What to avoid:

Arguing or defending aggressively
Disclosing customer information
Overly formal corporate language
Copy-paste identical responses

Platform-Specific Differences

Google Reviews: Most important for local SEO. Reply within 48 hours. Google considers response rate in ranking.

TripAdvisor: More travel-focused audience. Slightly more formal tone works better.

Yelp: Review-heavy culture — your responses are read carefully by community.

Airbnb: Hosts who respond to all reviews rank higher in search results.

The Time Problem

Most restaurant owners know they should respond to reviews. The problem is time.

A typical restaurant gets 3-8 reviews per week across platforms. Writing a professional response to each takes 5-10 minutes — that's up to 80 minutes per week just on review management.

The AI Solution

ReviewReply generates professional, platform-appropriate responses to any review in about 10 seconds.

Paste the review, select the platform, get a response you can post directly. Free for 3 per day — no signup required.

ReviewReply is part of the BaseAI Tools suite of AI-powered tools for small business owners.`,

How to Write an Invoice Reminder Email That Actually Gets Paid (With Templates)

Anders Dahl Rasmussen — Wed, 17 Jun 2026 04:52:21 +0000

How to Write an Invoice Reminder Email That Actually Gets Paid

Chasing unpaid invoices is one of the most uncomfortable parts of freelancing and running a small agency. Most people either avoid it for too long or send something so apologetic it doesn't create urgency.

Here's what actually works, based on patterns across thousands of invoice recovery situations.

The 3-tone framework

Your tone should shift based on how overdue the invoice is — not based on how you feel that day.

Days 1-7 — Gentle
Assume an honest oversight. No pressure. Warm closing.

Subject: Quick check-in on Invoice #1042

Hi [Name], hope you're doing well! Just wanted to flag that Invoice #1042 ($2,400) was due on [date] — it might have slipped through. Let me know if you need anything from my end to get it processed.

Days 8-21 — Firm
Direct and professional. Establish urgency without aggression.

Subject: Invoice #1042 — Payment Now 14 Days Overdue

Hi [Name], Invoice #1042 ($2,400) is now 14 days past its due date. Could you confirm when payment will be processed? Happy to answer any questions about the invoice.

Days 21+ — Final Notice
Serious, formal. State the next step clearly.

Subject: Final Notice — Invoice #1042

Hi [Name], I haven't received payment for Invoice #1042 ($2,400), now 30 days overdue. If I don't hear back by [date], I'll need to escalate this. I'd much rather resolve this directly — let me know how I can help move it forward.

Why specificity matters more than length

Short, specific emails outperform long explanations. Always include:

The exact invoice number
The exact amount
The original due date

Vague reminders get ignored. Specific ones get processed — because they're easy to act on.

Prevention beats collection

The best invoice chasing strategy is the one you never need:

Send invoices the same day work is delivered
Use Net 15 as your default (clients expect to negotiate down from Net 30 anyway)
A late fee clause (even 1.5%/month, rarely enforced) reduces late payments significantly

Automating this

I built a free tool that generates these emails automatically based on days overdue — InvoiceChaser. Paste in the client name, amount, and days overdue, and it picks the right tone and writes the email. There's also a $29 full recovery audit if you want a complete 14-day strategy with multiple templates and an escalation path.

No signup required, 3 free generations per day.

What's your invoice chasing strategy? Curious how others handle the gentle → firm → final transition.

Why Your Job Post Gets 200 Unqualified Applications (And How to Fix It)

Anders Dahl Rasmussen — Sat, 13 Jun 2026 18:51:07 +0000

Most small business owners write job posts from their own perspective. The result: either crickets, or a pile of applications from people who clearly didn't read the post.

Here's why — and what to do about it.

The Requirements Problem

The average job post has 40% unnecessary requirements. 'Must have 5+ years experience in [technology that's 3 years old]' isn't a requirement — it's a filter that eliminates good candidates while attracting people who exaggerate their CV.

The fix: split every requirement into MUST HAVE and NICE TO HAVE. Must-haves are things someone genuinely cannot do the job without. Everything else is a preference.

This single change typically increases qualified applications by 30-40%.

The Salary Transparency Problem

'Competitive salary' is a red flag to experienced candidates. It signals that either you haven't done market research, or the salary isn't actually competitive.

Adding a salary range — even a wide one — increases applications from qualified candidates, because those candidates stop self-selecting out of the process.

The Title Problem

Most job titles are written for internal clarity, not external searchability. 'Customer Experience Champion' ranks on zero job boards. 'Customer Support Manager' ranks on all of them.

Your title is a search keyword. Write it like one.

The 'About Us' Problem

Four paragraphs about your company history is four paragraphs that candidates skip. The best job posts limit 'About Us' to two sentences: what you do, and why it matters.

A Faster Fix

I built JobPostAI specifically for small business hiring managers who don't have an HR team. Paste in your role basics, get a complete structured job posting in 30 seconds — with proper requirements split, SEO-optimized title, and a clear CTA.

Free for 3 posts/day. No signup.

For deeper issues (why you're attracting the wrong people, specific keyword gaps, bias in your language), there's a $29 HiringAudit that covers the full analysis.

What's the worst job post mistake you've seen — as a candidate or a hiring manager?

Freelance Proposal Mistakes That Kill Your Win Rate (And How to Fix Each One)

Anders Dahl Rasmussen — Mon, 08 Jun 2026 14:03:00 +0000

After analyzing hundreds of freelance proposals (including many of my own failures), the same mistakes appear over and over.

None of them are about pricing too high. Most are structural.

Mistake 1: Opening with your bio

The first thing a client reads sets the entire tone.

The mistake:

"I am a full-stack developer with 10 years of experience specializing in React, Node.js, and AWS..."

Why it fails: The client already knows this. They posted a job for a developer, developers applied. You're signaling nothing except that you read other proposals and copied the format.

The fix: Open with the client's situation.

"Your checkout flow has a 68% abandonment rate. This proposal outlines how we fix the 3 technical bottlenecks causing it — and why the fix is faster than you might expect."

Same developer, completely different first impression.

Mistake 2: Vague deliverables

Deliverables that sound like tasks, not outcomes.

The mistake:

Build responsive frontend

Implement API integration

Database setup

Why it fails: These tell the client what you'll do, not what they'll receive. They're also completely impossible to dispute if there's a scope disagreement later.

The fix: Make deliverables measurable and specific.

Fully responsive frontend (mobile, tablet, desktop) with <2s load time

Integration with Stripe, tested end-to-end with 3 payment scenarios documented

PostgreSQL schema with migration scripts, seed data, and backup configuration

Now you have deliverables that both parties can verify.

Mistake 3: Price without an anchor

Presenting a number without context forces clients to imagine the worst.

The mistake:

Total investment: ,500

Why it fails: If the client was expecting ,000, seeing ,500 with no context creates immediate friction. If they were expecting 5,000, you just left money on the table.

The fix: Anchor before the number.

"A custom build of this scope from a digital agency would typically run 8,000-5,000. Working directly with me, your total investment is ,500 — with faster turnaround and direct communication throughout."

Now the number has context. ,500 feels like a deal, not a question.

Mistake 4: Multiple next steps

The end of most proposals looks like this:

"Let me know if you have any questions! Feel free to schedule a call, or reply with feedback, or we can also start with a smaller test project if you'd prefer..."

Why it fails: Ambiguity is the enemy of decisions. Giving three options means clients have to decide how to respond before they decide whether to respond. Most just don't.

The fix: One next step, stated simply.

"If this looks right, reply with 'Let's go' and I'll send the contract and first milestone invoice within the hour."

Concrete. Frictionless. Hard to overthink.

Mistake 5: Generic "why me" section

The section meant to differentiate usually doesn't.

The mistake:

Passionate about delivering high-quality code

Strong communicator

Attention to detail

Why it fails: Every developer says this. These aren't differentiators — they're table stakes.

The fix: Be specific about what you offer that others don't.

I've built 4 Stripe integrations in the last 18 months — I know exactly where the edge cases hide

I use Loom for async updates so you're never waiting for a scheduled call to know project status

I write handoff documentation as I build, not at the end — your team can maintain this without me

These are things another developer can't just claim to have.

The tool I built for this

If you want to generate proposals in this structure without writing from scratch, I built ProposalAI. Paste your brief, get a structured proposal back in 10 seconds. Free for 3/day.

There's also a quick audit mode — paste your existing proposal and get a score, win probability rating, and the top 3 things to fix.

Part of BaseAI Tools — AI micro-tools for small businesses and freelancers.

How to Write a Freelance Proposal That Actually Wins Clients (and the AI Tool I Built to Help)

Anders Dahl Rasmussen — Mon, 08 Jun 2026 14:02:32 +0000

I spent three years watching my freelance proposals get ignored. Good projects, competitive pricing, clients who seemed interested. Then nothing.

The problem wasn't my skills or my pricing.

It was that I wrote proposals from my perspective — what I'd build, how I'd build it, what my experience was. Clients don't care about any of that until they're convinced you understand their problem.

The 30-second test

Here's how clients actually read proposals:

They skim the opening — if it leads with "I am a developer with X years of experience," they already know this isn't different from the other 6 proposals sitting in their inbox.
They look for their company name — personalization signals effort.
They jump to the price — if there's no clear anchor, they'll fill in whatever number they fear most.

Most proposals fail step 1. They fail it because developers write them the way they'd explain a project to another developer.

The fix: flip the structure

Every winning proposal I've seen (and written, eventually) starts with the client's outcome, not the developer's credentials.

Before:

I am a full-stack developer with 8 years of experience in React and Node.js. I have built numerous similar applications...

After:

Your users are losing trust every time the dashboard fails to load their data in real time. This proposal outlines how we'll fix that — with a 3-week build plan, a technical approach that avoids the bottleneck you described, and a clear handoff checklist so your team can maintain it independently.

The second version demonstrates that you read the brief. The first version demonstrates that you have a LinkedIn profile.

The structure that wins

After running this pattern through dozens of proposals, here's the 8-section structure that consistently performs:

Executive Summary — 3 sentences, outcome-focused, no bio
Understanding Your Project — prove you get the real problem
Proposed Solution — specific tech choices, not generic "I'll use React"
Deliverables — measurable, not vague ("90+ Lighthouse score", not "fast website")
Timeline — phases with names and durations
Investment — price anchored to value, not just a number
Why Me — 3 differentiators, not generic "passionate developer" fluff
Next Steps — one action, not three

The free tool

I built ProposalAI to generate proposals in this structure automatically. You paste your project brief, it writes the proposal. Free for 3/day, no signup.

There's also a quick audit feature — paste your existing proposal and get a score, win probability, and the top 3 things to fix.

It uses this exact structure every time.

The goal wasn't to replace the effort of writing a good proposal — it was to remove the blank-page paralysis that makes most developers write safe, generic ones instead.

Built this as part of BaseAI Tools — a suite of AI micro-tools for small businesses.

How to Write an Airbnb Listing That Actually Ranks in Search

Anders Dahl Rasmussen — Sun, 07 Jun 2026 07:37:38 +0000

Airbnb's search algorithm doesn't care about your photos.

It cares about whether the words in your title match what guests type in the search bar.

The problem with most listings

Most Airbnb hosts write their listing from an owner's perspective: "Cozy apartment near the city centre. Great WiFi. Quiet neighbourhood."

That describes what you have. But guests don't search for "cozy apartment near city centre."

They search for: "self check-in apartment Paris" or "beach house pet friendly sleeps 6" or "studio with dedicated workspace."

If those phrases aren't in your listing, the algorithm can't match you.

The 3 elements that affect Airbnb search ranking

1. Title (most important)
Your title is matched directly against search queries. Every word slot is valuable. "Charming" and "beautiful" waste slots that could hold searchable phrases.

Better: Design Studio · 5min Walk Old Town · Superfast WiFi · Self Check-in

2. Description keyword density
Airbnb's algorithm reads your description. Amenity keywords that guests filter by ("dedicated workspace," "EV charging," "beach access") need to appear naturally.

3. Conversion rate
Listings that get clicked but not booked rank lower over time. Title and first photo drive this.

What a good listing rewrite looks like

Before: "Cozy apartment near city centre. Good wifi. Quiet area."

After: "Modern Studio · 8min Walk Colosseum · 200Mbps WiFi · Self Check-in · Perfect for Couples"

The second version matches 6 specific searches. The first matches almost none.

Try it free

HostAI rewrites your Airbnb listing title and description for search. 3 free per day, no account needed.

The rewrite takes 10 seconds. The difference in search visibility takes about 2 weeks to show up.

Etsy SEO in 2026: what actually moves your listings up in search

Anders Dahl Rasmussen — Thu, 04 Jun 2026 16:24:50 +0000

Etsy SEO in 2026: what actually moves listings up in search

Etsy's algorithm has changed significantly. Here's what matters now.

The three things Etsy actually ranks on

1. Title relevance — Etsy scans your title first. Front-load the exact phrase buyers search for.

Not: "Beautiful handcrafted sterling silver ring made with love"
Yes: "Sterling Silver Stacking Ring · Minimalist Band · Gift for Her"

2. Tags — All 13 tags should be different phrases, not repeats of your title. Use long-tail: "gifts for best friend under 50" beats "silver ring."

3. Conversion rate — Etsy measures how often people who see your listing actually buy. A better title → more relevant clicks → better conversion → higher ranking. It compounds.

What doesn't move the needle

Renewing listings (minimal effect, Etsy confirmed this)
Adding more photos (helps conversion slightly, not ranking directly)
Price alone (doesn't affect ranking)

The shortcut

Rewriting titles and tags properly takes 20-30 minutes per listing. Multiply that across a shop with 50+ products.

ContentBase does the rewrite in seconds — paste your current title and description, get an optimized version with SEO-targeted title, tags, and description. Free, no account.

Real before/after

Before: "Handmade wooden spoon with natural finish"

After: "Handmade Wooden Spoon · Cooking Utensil · Kitchen Gift · Natural Wood · Chef Gift · Rustic Kitchen Decor · Personalized Option Available"

That's 7 different search phrases in one title.

How to respond to negative restaurant reviews on Google (with examples)

Anders Dahl Rasmussen — Thu, 04 Jun 2026 16:24:42 +0000

How to respond to negative restaurant reviews on Google

The question "how do I respond to a bad Google review?" shows up on Quora, Reddit, and restaurant forums every day. Here's what actually works.

The wrong approaches

Defensive: "Actually our wait times are listed on our website." Nobody books again after reading this.

Over-apologetic: "We are so deeply sorry for this terrible experience and take full responsibility." Sounds corporate. Doesn't sound human.

Ignored: 47% of restaurants don't respond to negative reviews. These restaurants consistently underperform their responding competitors.

The formula that works

Name the specific complaint — not generic "your experience"
Accept it without excuse — even if the reviewer is partly wrong
One concrete next step — what you're doing about it
Invite them back — signals confidence

"Thank you for sharing this directly. A [specific complaint] is not the 
experience we want for anyone, and I take that seriously. 
[What we've done / are doing about it]. 
We'd genuinely value the chance to show you what a normal evening with us looks like."

The time problem

Most restaurant owners know this formula. They just don't have 20 minutes per review to write it.

That's the gap ReviewReply fills: paste the review, get a ready-to-publish professional response in 10 seconds. Free, no account.

Real example

Review: "Pasta was cold and the server was dismissive when we asked about it."

Generated response: "Thank you for taking the time to share this. Cold food is not acceptable regardless of how busy we are, and a dismissive response from your server is even less so. We've passed your feedback directly to both the kitchen and front-of-house team. If you're willing to give us another chance, please ask for the manager on arrival — we'd like to make it right in person."

Copy, paste, done.