Writing Right: 19 Tips for Keeping Your Site Copy Clean, Cool and Converting

February 21, 2019
0 minute read

A lot goes into building a great website for your clients. In addition to having the site look great and load quickly, the site also needs to be READABLE. Because even if you build the world’s fastest, slickest, most beautiful website, if the text is unclear, incorrect, unnecessarily complicated or badly written, it just isn’t... (more...) The post Writing Right: 19 Tips for Keeping Your Site Copy Clean, Cool and Converting appeared first on Duda Blog.

Whether someone on your team is writing the text for your sites or your clients are writing the content themselves, it never hurts to remind yourself how to write great website copy.

So, here are 19 tips (in no particular order) for keeping your site copy cool, clean and converting.

1. Write H1 texts that count

The H1 text on your website is very important. Not only is it the first text that visitors see when they reach your site, but it’s also the text that Google sees when it reads your site for SEO.

From a design perspective, text in the H1 tag is much larger than the rest of the text on the page, and it’s your job to make it meaningful, too. Make sure the text contains words that relate directly to the content of the site and make it crystal clear what the site is all about.

2. Pay attention to micro-copy, those short texts that say so much

Micro-copy is the short (usually) text that guides users through your site. Micro-copy prompts users to take certain actions. For example, the text on buttons, read more links, and contact form fields are all examples of micro-copy.

When writing micro-copy, being clear is very important, because if users don’t know what you want them to do, they are going to be confused. Some sites try to be cool instead of informative, but we recommend you stick with text that says exactly what the site visitor needs to know.

3. Be specific when possible

In the old days of the internet, it seems every other button read either “Start Now” or “Go Now”. Though these buttons can still be handy sometimes if you can offer visitors a more specific command, go for it. Say what you mean and don’t be afraid to use verbs. For example:

  • Read more
  • Watch now
  • Learn more
  • Watch video
  • Contact us

If you can let the user know what to expect, go for it.

4. Keep paragraphs short and concise

We recommend keeping texts short on your website, even when it comes to paragraphs. For example, if you’re explaining a service, describing a product, or writing about company history, you’re going to want to write a few sentences. In all of these cases, we recommend writing relatively short paragraphs, with relatively short sentences. If you have multiple paragraphs, use white space to break up the text so it is easier to read.

5. Add text in the image settings, too

Support the great images on your website s with clear descriptive text (as image attributes, not on the screen) so that the images are ‘visible’ to Google. This is important for SEO and enables screen readers to read the content of the images for visually impaired visitors.

6. Choose fonts wisely

Fonts have a huge impact on how people understand written texts. Fancy fonts make texts seem more complex. Simple fonts make texts more readable. Use bold fonts for headings and they’ll be more readable.

7. Capitalization matters

While some rules are meant to be broken, that doesn’t apply to the rules of capitalization. Do readers a favor. Follow the rules of capitalization on your site. It makes everything easier to understand .

8. Put a positive spin on your 404 pages

No one wants a site visitor to reach a 404 page, but it happens. While you may not be interested in creating a supercool 404 page for your customers, that doesn’t mean you can’t optimize this space with clever text that will redirect visitors to the right place on the site.

9. Make the most of placeholder texts

If you’ve got any type of contact form on your site, you’ve got placeholders. These are the empty fields where visitors are asked to add their email address, phone number, etc.

Don’t leave these fields empty, as visitors may not know quite what to write. Instead, use text that guides visitors (such as a mock email address or phone number). Visitors can use this text as a guide, so they fill in the form properly on their first try.

10. Write bios that are relatable & relevant

Many websites have a page dedicated to the company team. Large companies may have detailed descriptions of partners and founders only; smaller companies may have descriptions of everyone at the company.

Regardless of who you’re describing, keep the descriptions relatively short and relevant. Try to make the bios consistent too – it’s odd for one person to have a 4-paragraph bio and another person to have just two lines. Make the bios engaging and aligned with the look and feel of the site.

11. Write for the site’s audience

Not all audiences are the same, and site content should reflect this. Consider who the audience is and write for that audience. In other words, the language used in a real estate website would be different than that used for a surf shop.

12. Correct grammar is right for every audience

You can definitely write in different styles and tones for different audiences, but every audience deserves correct grammar. It may be cool, trendy, sophisticated, hip, elegant, for any age and population, but spelling and grammar should always be correct. If you’re not sure if something is correct (or if you’re not writing in your native language) find an editor or writer who can make sure everything is correct.

13. Don’t mess with eCommerce Text

While there are some areas of site content that you can certainly play with (bios, menu items, product names, etc.) when guiding site visitors to make a purchase, keep things as clear as possible. That means straightforward commands that clearly indicate what’s going to happen next.

Buy Now, Add to Cart and Go to Checkout are crystal clear instructions that should be kept that way.

14. Just the basics, please

If your customer has a contact form on their website, make sure every field in it brings valuable information. In other words, don’t ask visitors for information that your customer doesn’t need. Fax number? Favorite color? Probably not.

Including unnecessary fields waste site visitors’ time, but may turn them off from completing the form.

15. Use humor…with caution

Humor can be a great conversion tool, but there’s a fine line between humor and everything else. If there’s a chance that site visitors may find something offensive, rude or inappropriate, just leave it out.

16. Write for lazy readers

People visiting your website want information – they don’t want to read Dickens. So write simply, clearly, in short sentence and with short words. Your site isn’t a university entrance exam, so keep the language as simple as possible.

17. Take advantage of additional site pages

In some cases, may want to write more than a paragraph or two about a certain subject. For example, in describing a product or service. In such cases, instead of placing multiple paragraphs about a specific issue on a single page, considering a “Read more” button that links to another page that’s dedicated to that topic.

18. Jargon, be gone!

You may well use jargon in your office and when talking with colleagues, but we highly recommend keeping it off websites. You don’t know who’ll be reading your website, and there’s a good chance they may not be 100% familiar with your industry jargon. (This is particularly true for new customers…).

So keep the jargon to a minimum and keep the text readily and understandable.

19. Edit. Now edit again.

Don’t be satisfied with the first draft of anything. There is always room for improvement. So after you’ve written the first draft of your website, take a break and go for a walk in the forest.

When you come back to the text, be prepared to edit, revise and rewrite. Replace big words with smaller ones. Remove repetitive sentences and ideas. Make everything shorter.

That’s all there is to it

Of course, writing great content requires practice. The more you write, and the more you read about writing, the better your site copy will be.

Have tips to share with us about writing? Let us know in the comments below.


Did you find this article interesting?


Thanks for the feedback!
By Shawn Davis April 1, 2026
Core Web Vitals aren't new, Google introduced them in 2020 and made them a ranking factor in 2021. But the questions keep coming, because the metrics keep changing and the stakes keep rising. Reddit's SEO communities were still debating their impact as recently as January 2026, and for good reason: most agencies still don't have a clear, repeatable way to measure, diagnose, and fix them for clients. This guide cuts through the noise. Here's what Core Web Vitals actually measure, what good scores look like today, and how to improve them—without needing a dedicated performance engineer on every project. What Core Web Vitals measure Google evaluates three user experience signals to determine whether a page feels fast, stable, and responsive: Largest Contentful Paint (LCP) measures how long it takes for the biggest visible element on a page — usually a hero image or headline — to load. Google considers anything under 2.5 seconds good. Above 4 seconds is poor. Interaction to Next Paint (INP) replaced First Input Delay (FID) in March 2024. Where FID measures the delay before a user's first click is registered, INP tracks the full responsiveness of every interaction across the page session. A good INP score is under 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability — how much page elements unexpectedly move while content loads. A score below 0.1 is good. Higher scores signal that images, ads, or embeds are pushing content around after load, which frustrates users and tanks conversions. These three metrics are a subset of Google's broader Page Experience signals, which also include HTTPS, safe browsing, and mobile usability. Core Web Vitals are the ones you can most directly control and improve. Why your clients' scores may still be poor Core Web Vitals scores vary dramatically by platform, hosting, and how a site was built. Some of the most common culprits agencies encounter: Heavy above-the-fold content . A homepage with an autoplay video, a full-width image slider, and a chat widget loading simultaneously will fail LCP every time. The browser has to resolve all of those resources before it can paint the largest element. Unstable image dimensions . When an image loads without defined width and height attributes, the browser doesn't reserve space for it. It renders the surrounding text, then jumps it down when the image appears. That jump is CLS. Third-party scripts blocking the main thread . Analytics pixels, ad tags, and live chat tools run on the browser's main thread. When they stack up, every click and tap has to wait in line — driving INP scores up. A single slow third-party script can push an otherwise clean site into "needs improvement" territory. Too many web fonts . Each font family and weight is a separate network request. A page loading four font files before rendering any text will fail LCP, especially on mobile connections. Unoptimized images . JPEGs and PNGs served at full resolution, without compression or modern formats like WebP or AVIF, add unnecessary weight to every page load. How to measure them accurately There are two types of Core Web Vitals data you should be looking at for every client: Lab data comes from tools like Google PageSpeed Insights, Lighthouse, and WebPageTest. It simulates page loads in controlled conditions. Lab data is useful for diagnosing specific issues and testing fixes before you deploy them. Field data (also called Real User Monitoring, or RUM) comes from actual users visiting the site. Google collects this through the Chrome User Experience Report (CrUX) and surfaces it in Search Console and PageSpeed Insights. Field data is what Google actually uses as a ranking signal — and it often looks worse than lab data because it reflects real-world device and connection variability. If your client's site has enough traffic, you'll see field data in Search Console under Core Web Vitals. This is your baseline. Lab data helps you understand why the scores are what they are. For clients with low traffic who don't have enough field data to appear in CrUX, you'll be working primarily with lab scores. Set that expectation early so clients understand that improvements may not immediately show up in Search Console. Practical fixes that move the needle Fix LCP: get the hero image loading first The single most effective LCP improvement is adding fetchpriority="high" to the hero image tag. This tells the browser to prioritize that resource over everything else. If you're using a background CSS image for the hero, switch it to anelement — background images aren't discoverable by the browser's preload scanner. Also check whether your hosting serves images through a CDN with caching. Edge delivery dramatically reduces the time-to-first-byte, which feeds directly into LCP. Fix CLS: define dimensions for every media element Every image, video, and ad slot on the page needs explicit width and height attributes in the HTML. If you're using responsive CSS, you can still define the aspect ratio with aspect-ratio in CSS while leaving the actual size fluid. The key is giving the browser enough information to reserve space before the asset loads. Avoid inserting content above existing content after page load. This is common with cookie banners, sticky headers that change height, and dynamically loaded ad units. If you need to show these, anchor them to fixed positions so they don't push content around. Fix INP: reduce what's competing for the main thread Audit third-party scripts and defer or remove anything that isn't essential. Tools like WebPageTest's waterfall view or Chrome DevTools Performance panel show you exactly which scripts are blocking the main thread and for how long. Load chat widgets, analytics, and ad tags asynchronously and after the page's critical path has resolved. For most clients, moving non-essential scripts to load after the DOMContentLoaded event is a meaningful INP improvement with no visible impact on the user experience. For websites with heavy JavaScript — particularly those built on frameworks with large client-side bundles — consider breaking up long tasks into smaller chunks using the browser's Scheduler API or simply splitting components so the main thread isn't locked for more than 50 milliseconds at a stretch. What platforms handle automatically One of the practical advantages of building on a platform optimized for performance is that many of these fixes are applied by default. Duda, for example, automatically serves WebP images, lazy loads below-the-fold content, minifies CSS, and uses efficient cache policies for static assets. As of May 2025, 82% of sites built on Duda pass all three Core Web Vitals metrics — the highest recorded pass rate among major website platforms. That baseline matters when you're managing dozens or hundreds of client sites. It means you're starting each project close to or at a passing score, rather than diagnosing and patching a broken foundation. How much do Core Web Vitals actually affect rankings? Honestly, they're a tiebreaker — not a primary signal. Google has been clear that content quality and relevance still dominate ranking decisions. A well-optimized site with thin, irrelevant content won't outrank a content-rich competitor just because its CLS is 0.05. What Core Web Vitals do affect is the user experience that supports those rankings. Pages with poor LCP scores have measurably higher bounce rates. Sites with high CLS lose users mid-session. Those behavioral signals — time on page, return visits, conversions — are things search engines can observe and incorporate. The practical argument for fixing Core Web Vitals isn't just "because Google said so." It's that faster, more stable pages convert better. Every second of LCP improvement can reduce bounce rates by 15–20% depending on the industry and device mix. For client sites that monetize through leads or eCommerce, that's a revenue argument, not just an SEO argument. A repeatable process for agencies Audit every new site before launch. Run PageSpeed Insights and record LCP, INP, and CLS scores for both mobile and desktop. Flag anything in the "needs improvement" or "poor" range before the client sees the live site. Check Search Console monthly for existing clients. The Core Web Vitals report surfaces issues as they appear in field data. Catching a regression early — before it compounds — is significantly easier than explaining a traffic drop after the fact. Document what you've improved. Clients rarely see Core Web Vitals scores on their own. A monthly one-page performance summary showing before/after scores builds credibility and makes your technical work visible. Prioritize mobile. Google uses mobile-first indexing, and field data shows that mobile CWV scores are almost always worse than desktop. If you only have time to optimize one version, do mobile first. Core Web Vitals aren't a one-time fix. Platforms change, new scripts get added, campaigns bring in new widgets. Build the audit into your workflow and treat it like any other ongoing deliverable, and you'll stay ahead of the issues before they affect your clients' rankings. Duda's platform is built with Core Web Vitals performance in mind. Explore how it handles image optimization, script management, and site speed automatically — so your team spends less time debugging and more time building.
By Ilana Brudo March 31, 2026
Vertical SaaS must transition from tools to an AI-powered Vertical Operating System (vOS). Learn to leverage context, end tech sprawl, and maximize retention.
By Shawn Davis March 27, 2026
Automate client management, instant site generation, and data synchronization with an API-driven website builder to create a scalable growth engine for your SaaS platform.
Show More

Latest posts