<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Quicklity</title>
    <description>The latest articles on DEV Community by Quicklity (@quicklitytools).</description>
    <link>https://dev.to/quicklitytools</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209762%2F9850b3cb-cbda-4ea7-ba2c-3e88bcdb817c.png</url>
      <title>DEV Community: Quicklity</title>
      <link>https://dev.to/quicklitytools</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/quicklitytools"/>
    <language>en</language>
    <item>
      <title>Article Schema for Blog Posts: Help Google Understand Your Content</title>
      <dc:creator>Quicklity</dc:creator>
      <pubDate>Thu, 19 Nov 2026 05:18:23 +0000</pubDate>
      <link>https://dev.to/quicklitytools/article-schema-for-blog-posts-help-google-understand-your-content-e1i</link>
      <guid>https://dev.to/quicklitytools/article-schema-for-blog-posts-help-google-understand-your-content-e1i</guid>
      <description>&lt;p&gt;You can publish a great blog post and still leave Google guessing about it. The title is in an &lt;code&gt;h1&lt;/code&gt;, the author name is somewhere in a byline, the date is in small grey text — a human reader puts it all together in seconds, but a search engine has to infer it. Article schema removes that guesswork.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is Article schema?
&lt;/h2&gt;

&lt;p&gt;Article schema is structured data, written in JSON-LD, that tells search engines exactly what a page is: an article, who wrote it, when it was published, and what its headline and main image are. It uses vocabulary from Schema.org, and it lives in a &lt;code&gt;&amp;lt;script type="application/ld+json"&amp;gt;&lt;/code&gt; block in the page, invisible to readers but readable by search engines.&lt;/p&gt;

&lt;p&gt;There are two types you will meet most often:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Article&lt;/strong&gt; — the general type, suitable for news articles, reports and long-form pieces.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;BlogPosting&lt;/strong&gt; — a more specific subtype of Article, and the natural choice for a blog post.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your page is a blog post, use &lt;code&gt;BlogPosting&lt;/code&gt;. It is more precise, and precision is the whole point of structured data.&lt;/p&gt;

&lt;h2&gt;
  
  
  The key fields
&lt;/h2&gt;

&lt;p&gt;You do not need every property Schema.org defines. These are the ones that matter most for a blog post:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;headline&lt;/strong&gt; — the title of the article, exactly as it appears on the page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;author&lt;/strong&gt; — the person (or organisation) who wrote it. Use a &lt;code&gt;Person&lt;/code&gt; object with a &lt;code&gt;name&lt;/code&gt;, and a &lt;code&gt;url&lt;/code&gt; to the author's profile when you have one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;datePublished&lt;/strong&gt; — the original publication date, in ISO 8601 format, for example &lt;code&gt;2026-11-19&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;dateModified&lt;/strong&gt; — the date the article was last updated. Keep this honest: update it only when the content actually changes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;image&lt;/strong&gt; — the main image of the article, as a full URL. It should be the image a reader actually sees at the top of the post.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;description&lt;/strong&gt; — a short summary of the article.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;mainEntityOfPage&lt;/strong&gt; — the URL of the page the article lives on, which ties the schema to the page itself.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A JSON-LD example
&lt;/h2&gt;

&lt;p&gt;Here is a complete, minimal example for a blog post:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"BlogPosting"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"headline"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Article Schema for Blog Posts: Help Google Understand Your Content"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"How Article and BlogPosting schema help search engines understand a blog post, and how to add them correctly."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"author"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Person"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Quicklity"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://quicklitytools.com"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"datePublished"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2026-11-19"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"dateModified"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2026-11-19"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"image"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://quicklitytools.com/images/article-schema-example.jpg"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"mainEntityOfPage"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"WebPage"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/blog/article-schema-for-blog-posts"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Paste a block like this into the &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt; of your blog post page, replacing the values with your own. That is genuinely all there is to it — no plugin required if you can edit the page HTML.&lt;/p&gt;

&lt;h2&gt;
  
  
  The golden rule: match what readers can see
&lt;/h2&gt;

&lt;p&gt;This is the rule most people get wrong. Every value in your schema must match content that is actually visible on the page:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The &lt;code&gt;headline&lt;/code&gt; must be the headline on the page, not a keyword-stuffed alternative.&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;author&lt;/code&gt; must be the author shown in the byline.&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;datePublished&lt;/code&gt; must be the date shown to readers.&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;image&lt;/code&gt; must be an image that appears in the article.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Adding a different author, a fake date, a stock image that never appears on the page, or a headline that does not exist on the page is misleading markup. Google can ignore it, and repeated misleading markup can cost you the rich-result eligibility you were trying to earn. Write the article first, then describe it accurately in schema — never the other way round.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test before you publish
&lt;/h2&gt;

&lt;p&gt;Always test the page before it goes live, and again after any template change:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open Google's Rich Results Test and enter the page URL (or paste the code).&lt;/li&gt;
&lt;li&gt;Check that the Article/BlogPosting item is detected with no errors.&lt;/li&gt;
&lt;li&gt;Fix any warnings about missing recommended fields, such as &lt;code&gt;image&lt;/code&gt; or &lt;code&gt;author&lt;/code&gt;, where you can.&lt;/li&gt;
&lt;li&gt;Re-test after fixing — a small typo in JSON, like a missing comma, breaks the whole block.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The Schema.org validator is also worth a run for a second opinion, since it checks the markup against the full vocabulary rather than only what Google displays.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes to avoid
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Copy-pasting the same schema onto every post.&lt;/strong&gt; Each article needs its own headline, dates and image.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forgetting &lt;code&gt;dateModified&lt;/code&gt;.&lt;/strong&gt; Updating a post without updating the date — or updating the date without changing the content — both erode trust.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Using Article when the page is not an article.&lt;/strong&gt; A product page, a homepage or a category page is not a blog post; use the schema type that fits the page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hiding the data.&lt;/strong&gt; Schema that describes content nobody can see on the page is exactly what Google warns against.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Invalid JSON.&lt;/strong&gt; One trailing comma or unescaped quote silently invalidates the block. Validate, don't assume.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Generate it instead of hand-writing it
&lt;/h2&gt;

&lt;p&gt;If you would rather not write JSON-LD by hand, a generator does the formatting for you. Fill in the headline, author, dates and image URL, and it produces a ready-to-paste block: &lt;a href="https://quicklitytools.com/schema-markup-generator" rel="noopener noreferrer"&gt;Schema Markup Generator&lt;/a&gt;. Whichever route you take, run the result through the Rich Results Test before publishing.&lt;/p&gt;

&lt;p&gt;Article schema will not turn a weak post into a good one, and it is not a ranking guarantee. What it does is make a good post easier for Google to understand — who wrote it, when, and what it is about. For a blogger, that is a cheap, one-time improvement worth making on every post.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>schema</category>
      <category>seo</category>
      <category>blog</category>
    </item>
    <item>
      <title>UTM Parameters for Social Media: Track Every Click Back to Its Post</title>
      <dc:creator>Quicklity</dc:creator>
      <pubDate>Mon, 16 Nov 2026 13:47:30 +0000</pubDate>
      <link>https://dev.to/quicklitytools/utm-parameters-for-social-media-track-every-click-back-to-its-post-30p9</link>
      <guid>https://dev.to/quicklitytools/utm-parameters-for-social-media-track-every-click-back-to-its-post-30p9</guid>
      <description>&lt;p&gt;Social media sends you traffic every day, but without UTM parameters, most of it arrives as one big mystery blob in your analytics. You can see that people came from "social", but you cannot tell which post, which platform, or which campaign brought them. UTM parameters fix that. They are small tags you add to a link so every click carries its own story back to Google Analytics.&lt;/p&gt;

&lt;h2&gt;
  
  
  The five parameters, and what they mean on social
&lt;/h2&gt;

&lt;p&gt;There are five UTM parameters. On social media, four of them do the heavy lifting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;utm_source&lt;/strong&gt; — where the traffic came from. Use the platform name: instagram, facebook, linkedin, x, tiktok.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;utm_medium&lt;/strong&gt; — how it arrived. Use &lt;code&gt;social&lt;/code&gt; for organic posts and &lt;code&gt;cpc&lt;/code&gt; for paid ads. This one distinction keeps your free and paid traffic from getting mixed up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;utm_campaign&lt;/strong&gt; — the campaign or push behind the post, like &lt;code&gt;november-launch&lt;/code&gt; or &lt;code&gt;winter-sale&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;utm_content&lt;/strong&gt; — which exact post or variant the click came from. This is the one most people skip, and it is the one that tells you which post actually worked.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;utm_term&lt;/strong&gt; — skip this one on social. It is meant for paid search keywords, not social posts.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A real example
&lt;/h2&gt;

&lt;p&gt;Say you share a link to your new guide on Instagram and on LinkedIn. Without UTMs, both clicks look the same. With UTMs, they look like this:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;https://quicklitytools.com/utm-builder?utm_source=instagram&amp;amp;utm_medium=social&amp;amp;utm_campaign=november-launch&amp;amp;utm_content=story-swipe-up&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;code&gt;https://quicklitytools.com/utm-builder?utm_source=linkedin&amp;amp;utm_medium=social&amp;amp;utm_campaign=november-launch&amp;amp;utm_content=feed-post&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Same destination, same campaign — but now you can see exactly which platform and which post sent each visitor.&lt;/p&gt;

&lt;h2&gt;
  
  
  Naming rules that keep your reports clean
&lt;/h2&gt;

&lt;p&gt;UTM values are case-sensitive, so &lt;code&gt;Instagram&lt;/code&gt; and &lt;code&gt;instagram&lt;/code&gt; show up as two different sources in GA4. Pick one style and stick to it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Always use lowercase.&lt;/li&gt;
&lt;li&gt;Use hyphens instead of spaces: &lt;code&gt;winter-sale&lt;/code&gt;, not &lt;code&gt;winter sale&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Keep a short list of allowed sources and mediums, and reuse them. If every post invents a new spelling, your reports turn into a mess.&lt;/li&gt;
&lt;li&gt;Give every campaign a clear, short name before you start posting, not after.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A free tool like the Quicklity UTM Builder (&lt;a href="https://quicklitytools.com/utm-builder" rel="noopener noreferrer"&gt;https://quicklitytools.com/utm-builder&lt;/a&gt;) builds these links for you, so you do not have to type the parameters by hand and risk a typo.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where to see the results in GA4
&lt;/h2&gt;

&lt;p&gt;Once your tagged links are live, open GA4 and go to Reports, then Acquisition, then Traffic acquisition. Look at the Session source / medium and Session campaign columns. Your tagged social clicks will show up as &lt;code&gt;instagram / social&lt;/code&gt;, &lt;code&gt;linkedin / social&lt;/code&gt;, and so on, with the campaign name beside them. If a post drove traffic, you will see it there by name instead of guessing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes to avoid
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tagging links inside your own site or app.&lt;/strong&gt; UTMs are for traffic coming in from outside. Tagging internal links overwrites the real source of the visit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Using a different spelling every time.&lt;/strong&gt; One campaign called &lt;code&gt;nov-launch&lt;/code&gt;, another &lt;code&gt;NovemberLaunch&lt;/code&gt;, and a third &lt;code&gt;november_launch&lt;/code&gt; will split one campaign into three in your reports.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forgetting utm_content.&lt;/strong&gt; Without it, you know the platform but not the post. When two posts share one campaign, utm_content is what separates the winner from the flop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Never testing the link.&lt;/strong&gt; Click it yourself before you post. A broken or mistyped UTM link still works as a link — it just silently reports nothing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Start with one campaign
&lt;/h2&gt;

&lt;p&gt;You do not need a complicated system. Pick your next campaign, write down the source, medium, campaign, and content values in advance, build each link with a UTM builder, and check GA4 after a few days. Once you can trace a click back to the exact post that earned it, you will know which content deserves more of your time — and which does not.&lt;/p&gt;

</description>
      <category>utm</category>
      <category>analytics</category>
      <category>marketing</category>
      <category>socialmedia</category>
    </item>
    <item>
      <title>How to Track Email Campaigns with UTM Parameters</title>
      <dc:creator>Quicklity</dc:creator>
      <pubDate>Thu, 12 Nov 2026 05:18:46 +0000</pubDate>
      <link>https://dev.to/quicklitytools/how-to-track-email-campaigns-with-utm-parameters-303d</link>
      <guid>https://dev.to/quicklitytools/how-to-track-email-campaigns-with-utm-parameters-303d</guid>
      <description>&lt;p&gt;You send a newsletter, a few people click through, and a sale happens a day later. Which email deserves the credit? Without UTM parameters, Google Analytics will usually lump that visit under something vague like "email" or "direct", and you will have no way to tell whether your welcome email, your weekly newsletter or a one-off promotion did the work.&lt;/p&gt;

&lt;p&gt;UTM parameters fix that. They are short tags you add to a link so Analytics can record exactly where a click came from. In this guide, you will learn which parameters to use for email, how to name them consistently, how to build a tracked link, and how to check the results in GA4.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why email tracking needs UTMs
&lt;/h2&gt;

&lt;p&gt;Most email tools already tell you open and click rates, but they cannot tell you what happened after the click. Did readers buy, sign up or leave after ten seconds? Analytics can answer that, but only if it knows the visit came from email in the first place.&lt;/p&gt;

&lt;p&gt;That is the problem UTMs solve. When someone clicks a tagged link, the tags travel with them to your site and are stored as the session's source, medium and campaign. Without them, email traffic is often reported as direct traffic, which makes email look far less effective than it really is. With them, every email has a clear, comparable record.&lt;/p&gt;

&lt;h2&gt;
  
  
  The five UTM parameters — and the four you need for email
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;utm_source&lt;/strong&gt; — who sent the traffic. For email, use the name of your email tool or list, for example &lt;code&gt;mailchimp&lt;/code&gt;, &lt;code&gt;convertkit&lt;/code&gt; or &lt;code&gt;newsletter&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;utm_medium&lt;/strong&gt; — the channel. For email, this is almost always &lt;code&gt;email&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;utm_campaign&lt;/strong&gt; — the specific email or series, for example &lt;code&gt;november-newsletter&lt;/code&gt; or &lt;code&gt;welcome-series&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;utm_content&lt;/strong&gt; — what was clicked, for example &lt;code&gt;header-button&lt;/code&gt;, &lt;code&gt;hero-image&lt;/code&gt; or &lt;code&gt;footer-link&lt;/code&gt;. Use this when one email has several links to the same page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;utm_term&lt;/strong&gt; — the keyword, mainly for paid search. You can leave this out for email.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Only the first three are essential, but utm_content is very useful. It tells you whether people clicked the main call to action or a small text link at the bottom.&lt;/p&gt;

&lt;h2&gt;
  
  
  Naming rules that keep your reports clean
&lt;/h2&gt;

&lt;p&gt;UTM values are case-sensitive, so &lt;code&gt;Email&lt;/code&gt;, &lt;code&gt;email&lt;/code&gt; and &lt;code&gt;EMAIL&lt;/code&gt; appear as three different mediums in GA4. Pick one style and stick to it. Lowercase, with hyphens instead of spaces, is the safest choice.&lt;/p&gt;

&lt;p&gt;Keep names short, descriptive and consistent. Use &lt;code&gt;welcome-series&lt;/code&gt; every time, not &lt;code&gt;welcome_series&lt;/code&gt; one week and &lt;code&gt;welcome-series-2&lt;/code&gt; the next. Agree the pattern before you send anything: source is the tool, medium is always &lt;code&gt;email&lt;/code&gt;, campaign is the email name, and content is the link position.&lt;/p&gt;

&lt;p&gt;Avoid spaces and special characters, and do not change a campaign name halfway through a series. If you do, GA4 will split the results and you will have to add them together by hand.&lt;/p&gt;

&lt;h2&gt;
  
  
  A worked example
&lt;/h2&gt;

&lt;p&gt;Suppose you run a small online shop and send a November newsletter with a 20% discount. The main button links to your sale page. A clean set of values would be:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Source: &lt;code&gt;mailchimp&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Medium: &lt;code&gt;email&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Campaign: &lt;code&gt;november-newsletter&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Content: &lt;code&gt;main-offer-button&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That gives you this link:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;https://example.com/sale?utm_source=mailchimp&amp;amp;utm_medium=email&amp;amp;utm_campaign=november-newsletter&amp;amp;utm_content=main-offer-button&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;If the same email also links to the sale page from a text link lower down, keep the first three values the same and change only utm_content to &lt;code&gt;text-link&lt;/code&gt;. Now GA4 can show you which link earned more clicks and, more importantly, which one earned more sales. That is a far better test than guessing from click totals alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building the link without typing it by hand
&lt;/h2&gt;

&lt;p&gt;You do not need to assemble these URLs manually, and you should not — a missing &lt;code&gt;?&lt;/code&gt; or &lt;code&gt;&amp;amp;&lt;/code&gt; breaks the whole tag. Paste your destination URL into a UTM builder, fill in source, medium, campaign and content, and copy the finished link into your email.&lt;/p&gt;

&lt;p&gt;You can use the free &lt;a href="https://quicklitytools.com/utm-builder" rel="noopener noreferrer"&gt;Quicklity UTM Builder&lt;/a&gt; for this. It builds the link in the correct format, so you only have to think about the values, not the punctuation. Always test the finished link before you send: click it, check that it opens the right page, and check that the UTM values are still in the address bar.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checking the results in GA4
&lt;/h2&gt;

&lt;p&gt;Give GA4 a day to process the data, then go to Reports &amp;gt; Acquisition &amp;gt; Traffic acquisition. Look for the session source/medium &lt;code&gt;mailchimp / email&lt;/code&gt;, then add campaign as a secondary dimension or use the search box to filter for &lt;code&gt;november-newsletter&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Compare campaigns on the numbers that matter: sessions, engaged sessions, conversions and revenue, not just clicks. A campaign with fewer clicks but more purchases is the better campaign. You can also build an Exploration report, breaking the same campaign down by utm_content to compare each link.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes to avoid
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tagging internal links.&lt;/strong&gt; Only tag links in the email itself. Never add UTMs to links inside your own website — they will start a new session and distort your source data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Using a different campaign name for every send.&lt;/strong&gt; A series should share one campaign name so you can see its total result.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inconsistent capitalisation.&lt;/strong&gt; Decide on lowercase once, and do not vary it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forgetting to test.&lt;/strong&gt; Send yourself a test email and click every tracked link before the real send.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Judging by clicks alone.&lt;/strong&gt; A link can win on clicks and lose on sales. Always check conversions too.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Start with your next email
&lt;/h2&gt;

&lt;p&gt;You do not need a new tool or a complicated setup to track email properly. Pick one naming pattern, apply it to your next email, and check the result in GA4 the following day. After two or three sends, you will know which offers and link positions actually bring people back to your site — and which ones only look busy. That is the difference between sending email and learning from it.&lt;/p&gt;

</description>
      <category>marketing</category>
      <category>analytics</category>
    </item>
    <item>
      <title>Schema Markup for Local Businesses: The 5 Types That Actually Matter</title>
      <dc:creator>Quicklity</dc:creator>
      <pubDate>Mon, 09 Nov 2026 05:20:28 +0000</pubDate>
      <link>https://dev.to/quicklitytools/schema-markup-for-local-businesses-the-5-types-that-actually-matter-7fl</link>
      <guid>https://dev.to/quicklitytools/schema-markup-for-local-businesses-the-5-types-that-actually-matter-7fl</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Updated 16 November 2026:&lt;/strong&gt; This guide has been updated to put the entity facts first. The LocalBusiness and Organization details that identify your business — a stable &lt;a class="mentioned-user" href="https://dev.to/id"&gt;@id&lt;/a&gt;, sameAs links, geo coordinates, areaServed, and consistent NAP details — now come before the other schema types, and the notes on FAQPage and AggregateRating have been moved to the end with clearer caveats about when they produce a visible result.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;When someone searches for a plumber near them, a café that is open now, or a dentist with good reviews, Google does more than rank web pages. It tries to understand real businesses: where they are, when they are open, what they do, and what customers think of them.&lt;/p&gt;

&lt;p&gt;Schema markup is the structured data that helps search engines understand those facts. It is a small block of code, usually written in JSON-LD, that describes your business in a format machines can read easily. It does not change what visitors see on your page, but it can help Google show richer and more useful results.&lt;/p&gt;

&lt;p&gt;That does not mean every business needs every type of schema. For most local businesses, five types cover almost everything that matters. Start with those, get them right, and ignore the rest until you have a clear reason to add more.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the entity foundation
&lt;/h2&gt;

&lt;p&gt;Before adding any other type, get the facts about your business right in one place. This is the highest-priority part of local schema, because everything else builds on it.&lt;/p&gt;

&lt;p&gt;In your LocalBusiness or Organization markup, include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A stable &lt;code&gt;@id&lt;/code&gt; — one permanent URL that identifies the business, such as the homepage or the location page, used consistently everywhere.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;sameAs&lt;/code&gt; links to your Google Business Profile and your other real profiles, so search engines can connect the same business across the web.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;geo&lt;/code&gt; coordinates for the business location.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;areaServed&lt;/code&gt;, describing the towns, cities, or regions you actually serve.&lt;/li&gt;
&lt;li&gt;An identical NAP — name, address, and phone number — on your website, your Google Business Profile, and local directories. Even small differences, such as an old phone number or a different spelling of the address, can confuse search engines.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If these facts are inconsistent or missing, extra schema types will not fix the problem. Get the entity facts right first, keep them the same everywhere, and only then add the types below.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why local businesses benefit
&lt;/h2&gt;

&lt;p&gt;Local search is competitive, and small details can make a difference. Clear LocalBusiness markup can help Google connect your website with your address, your service area, and your Google Business Profile. Breadcrumbs can make your pages easier to understand. FAQ and review markup can make your answers and ratings eligible for expanded results in some cases, although visible displays are limited — see the notes under sections 4 and 5 below.&lt;/p&gt;

&lt;p&gt;None of this is guaranteed. Google decides which rich results to show, and when. Think of schema as giving Google accurate, well-organised information — not as a switch that forces a particular display. The benefit is better understanding, and better understanding can lead to better visibility in local results and the local pack.&lt;/p&gt;

&lt;h2&gt;
  
  
  The golden rule: match what visitors can see
&lt;/h2&gt;

&lt;p&gt;Before choosing a type, remember one rule: your markup must match the content on the page. If your opening hours, address, prices, services, or reviews appear in your schema, visitors should be able to see the same information on that page.&lt;/p&gt;

&lt;p&gt;Do not add markup for services you do not offer, reviews you have not received, or opening hours that are not shown anywhere. If the markup and the visible page do not match, Google may ignore the markup — and repeated mismatches can damage trust in your site.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. LocalBusiness
&lt;/h2&gt;

&lt;p&gt;This is the foundation for almost every local business. Use the most specific subtype that fits, such as Dentist, Restaurant, HairSalon, or Plumber, rather than the generic LocalBusiness type when a closer match exists.&lt;/p&gt;

&lt;p&gt;Include your business name, address, telephone number, website, and the area you serve. Keep these details identical everywhere they appear online, including your website, your Google Business Profile, and local directories. Small differences, such as a changed phone number or an old address, can confuse search engines.&lt;/p&gt;

&lt;p&gt;If you have more than one location, give each location its own page and its own LocalBusiness markup. One block that tries to describe several branches usually creates confusion rather than clarity.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. OpeningHoursSpecification
&lt;/h2&gt;

&lt;p&gt;OpeningHoursSpecification is part of LocalBusiness markup, but it deserves attention on its own. It tells search engines when your business is open, including regular hours, seasonal changes, and holiday closures.&lt;/p&gt;

&lt;p&gt;This matters because Google often shows “open now” or “closes at” information in local results. If your hours in schema are wrong, customers may arrive when you are closed, or avoid visiting when you are actually open.&lt;/p&gt;

&lt;p&gt;Keep your hours updated in both your schema and your Google Business Profile. If you change your hours for a holiday, update both places at the same time.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. BreadcrumbList
&lt;/h2&gt;

&lt;p&gt;BreadcrumbList describes the path to a page, such as Home &amp;gt; Services &amp;gt; Emergency Plumbing. It helps search engines understand the structure of your site and can make your listing in search results easier to read.&lt;/p&gt;

&lt;p&gt;Breadcrumbs are especially useful for multi-location businesses and for service pages that sit several levels deep in a site. If your site already shows breadcrumbs to visitors, mark them up. If it does not, adding them can help both visitors and search engines.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to use the Quicklity Schema Markup Generator
&lt;/h2&gt;

&lt;p&gt;Writing JSON-LD by hand is easy to get wrong. A missing comma or a wrong property name can break the whole block. The free &lt;a href="https://quicklitytools.com/tools/schema-markup-generator" rel="noopener noreferrer"&gt;Quicklity Schema Markup Generator&lt;/a&gt; creates a ready-to-use JSON-LD block for your business. Fill in your details, copy the result, and paste it into your page.&lt;/p&gt;

&lt;p&gt;After adding schema to a page, test it with Google’s Rich Results Test or the Schema.org validator. Fix any errors the tool reports, and re-check after you change your business details.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes to avoid
&lt;/h2&gt;

&lt;p&gt;Many local businesses add schema once and never check it again. These mistakes are common:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Adding reviews that are not visible on the page, or that were never collected&lt;/li&gt;
&lt;li&gt;Marking up services the business does not offer&lt;/li&gt;
&lt;li&gt;Using the wrong business type, such as LocalBusiness when a more specific type exists&lt;/li&gt;
&lt;li&gt;Copying FAQ markup from another page instead of writing questions customers actually ask&lt;/li&gt;
&lt;li&gt;Forgetting to update hours, phone numbers, or addresses after a change&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Review your schema when you change anything about your business. A quick check takes minutes and can prevent weeks of incorrect information in search results.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. FAQPage — useful markup, but rarely a visible rich result
&lt;/h2&gt;

&lt;p&gt;Many local business pages already answer common questions: how much does it cost, how do I book, is there parking, what is your cancellation policy? FAQPage markup can make those questions and answers eligible for rich results.&lt;/p&gt;

&lt;p&gt;Write the questions exactly as customers ask them, and keep each answer short and direct. Only mark up questions that are actually answered on the page, and do not use FAQ markup for advertising copy or for questions with no real answer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important caveat:&lt;/strong&gt; Google has restricted FAQ rich results to a small set of authoritative sites, mainly government and health sites. A typical local business should not expect a visible FAQ rich result, even with correct FAQPage markup. The markup is still harmless if it matches the page, and it can help search engines understand the questions you answer — but treat it as a low-priority addition, not as a way to win extra space in search results.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Review and AggregateRating — useful markup, but do not expect stars
&lt;/h2&gt;

&lt;p&gt;Reviews are powerful for local businesses, and schema can help search engines understand them. If genuine customers have reviewed your business, AggregateRating can summarise the average rating and the number of reviews. Individual Review markup can describe a specific customer's experience.&lt;/p&gt;

&lt;p&gt;Only use reviews that are real, visible on your site, and collected fairly. Never invent reviews, copy reviews from another site, or mark up testimonials that visitors cannot see. Google is strict about this, and fake review markup is one of the fastest ways to lose eligibility for rich results.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important caveat:&lt;/strong&gt; Google does not show review stars for ratings a business marks up about itself on its own LocalBusiness pages. So even with correct AggregateRating markup, a local business should not expect stars to appear beside its own listing. Keep review markup only for genuine, visible reviews, and treat it as a way to help search engines understand your reputation — not as a way to display stars.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Schema markup will not fix a weak website or a business with no real presence, but for a genuine local business it is one of the simplest technical improvements you can make. It helps Google understand who you are, where you are, and what you offer.&lt;/p&gt;

&lt;p&gt;Start with LocalBusiness, add opening hours and breadcrumbs, and use FAQ and review markup only where they genuinely apply. Keep every fact consistent, keep the markup honest, and test your pages after every change.&lt;/p&gt;

&lt;p&gt;You can generate a valid JSON-LD block for your business with the free &lt;a href="https://quicklitytools.com/tools/schema-markup-generator" rel="noopener noreferrer"&gt;Quicklity Schema Markup Generator&lt;/a&gt; — paste the result into your page, then check it with a schema validator before publishing.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Where Your UTM Campaigns Actually Appear in GA4 — and Why Some Go Missing</title>
      <dc:creator>Quicklity</dc:creator>
      <pubDate>Thu, 05 Nov 2026 05:14:51 +0000</pubDate>
      <link>https://dev.to/quicklitytools/where-your-utm-campaigns-actually-appear-in-ga4-and-why-some-go-missing-4c2n</link>
      <guid>https://dev.to/quicklitytools/where-your-utm-campaigns-actually-appear-in-ga4-and-why-some-go-missing-4c2n</guid>
      <description>&lt;p&gt;You built the tagged links, shared them, and waited. Then you opened Google Analytics 4 and could not find the campaign where you expected it. That is more common than you might think, and it is usually a reading problem, not a tracking failure.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where UTM data shows up in GA4
&lt;/h2&gt;

&lt;p&gt;In GA4, UTM values are translated into session dimensions. In most cases, &lt;code&gt;utm_source&lt;/code&gt; becomes session source, &lt;code&gt;utm_medium&lt;/code&gt; becomes session medium, and &lt;code&gt;utm_campaign&lt;/code&gt; becomes session campaign. The simplest place to start is Reports, then Traffic acquisition. There, you can look at session source, medium and campaign together, and see sessions, engaged sessions and conversions for each combination.&lt;/p&gt;

&lt;p&gt;If you want a cleaner view, build an exploration or a report filtered by session campaign. That lets you answer a narrower question, such as how one launch performed across email, social and paid search, without the rest of your traffic getting in the way.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to read the report without fooling yourself
&lt;/h2&gt;

&lt;p&gt;First, check the date range and compare it with the dates you actually ran the campaign. A link shared on Monday will not explain traffic from the previous week. Next, read source, medium and campaign as one set. Looking at campaign alone can hide the fact that the same campaign name is arriving from very different places.&lt;/p&gt;

&lt;p&gt;Also remember what a session dimension means. It describes the session that started with that tagged visit, not every later visit by the same person. If someone returns directly a week later, that later session will not carry the original campaign. That is normal behaviour, and it is one reason campaign numbers rarely match clicks on the platform that sent the traffic.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common tagging mistakes that split or hide campaigns
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Inconsistent capitalisation and spelling. &lt;code&gt;Facebook&lt;/code&gt;, &lt;code&gt;facebook&lt;/code&gt; and &lt;code&gt;fb&lt;/code&gt; become separate sources. Pick lowercase names and stick to them.&lt;/li&gt;
&lt;li&gt;Putting UTMs on internal links. That overwrites the original source, so a visit that began on social media can end up looking like it came from your own site.&lt;/li&gt;
&lt;li&gt;Swapping source and medium. Source is where the visit came from, medium is the kind of traffic, such as social, email or cpc, and campaign is the name of the promotion.&lt;/li&gt;
&lt;li&gt;Reusing one vague campaign name for everything. If every link is &lt;code&gt;launch&lt;/code&gt;, you cannot compare channels or dates.&lt;/li&gt;
&lt;li&gt;Letting redirects or shortened links drop the parameters. Always click the final link and confirm the UTMs survive to the landing page.&lt;/li&gt;
&lt;li&gt;Changing the naming halfway through a campaign. That splits one campaign into two rows and makes week-by-week comparison misleading.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A simple workflow that keeps reports readable
&lt;/h2&gt;

&lt;p&gt;Write the source, medium and campaign down before you create the link. Use the same format every time, test the link once, and then check GA4 after the first real clicks to confirm the campaign appears exactly as you named it. A consistent builder helps here: the free UTM Builder at &lt;a href="https://quicklitytools.com/utm-builder" rel="noopener noreferrer"&gt;https://quicklitytools.com/utm-builder&lt;/a&gt; keeps the format in one place, so you are less likely to improvise a slightly different name on the next link.&lt;/p&gt;

&lt;p&gt;The goal is not perfect attribution. It is a report you can trust enough to decide where to spend the next effort. Consistent tags, read in Traffic acquisition by session source, medium and campaign, give you exactly that.&lt;/p&gt;

</description>
      <category>analytics</category>
    </item>
    <item>
      <title>Schema Markup Without Code: A Beginner's Guide to Rich Results</title>
      <dc:creator>Quicklity</dc:creator>
      <pubDate>Mon, 02 Nov 2026 02:04:31 +0000</pubDate>
      <link>https://dev.to/quicklitytools/schema-markup-without-code-a-beginners-guide-to-rich-results-3lf6</link>
      <guid>https://dev.to/quicklitytools/schema-markup-without-code-a-beginners-guide-to-rich-results-3lf6</guid>
      <description>&lt;p&gt;If you have heard that schema markup can help your pages appear with extra details in search results, but you do not write code, this guide is for you. You do not need to learn a programming language to start, and you do not need to add markup to every page on day one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What schema markup actually is
&lt;/h2&gt;

&lt;p&gt;Schema markup is structured data: a clear, machine-readable description of what a page is about. Most beginners meet it as JSON-LD, a small block of code placed in a page that describes, for example, an article, a product, a recipe, a frequently asked question, or a local business.&lt;/p&gt;

&lt;p&gt;Think of it this way. Your visible page tells people what the content is. Schema tells search engines the same thing in a structured form they can process more easily. It does not change how the page looks to visitors.&lt;/p&gt;

&lt;p&gt;A rich result is an enhanced search appearance, such as extra details under a listing. Schema can make a page eligible for consideration for such an appearance, but it does not guarantee one, and it does not by itself guarantee higher rankings.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pick the right type first
&lt;/h2&gt;

&lt;p&gt;Choosing the type before you generate any code saves most beginners from the most common mistakes. Ask: what is this page, in one sentence?&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Article or BlogPosting&lt;/strong&gt; for a blog post or news article.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FAQPage&lt;/strong&gt; for a page with visible questions and answers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Product&lt;/strong&gt; for a product page, with details such as price and availability where they genuinely apply.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LocalBusiness&lt;/strong&gt; for a business page, with its name, address and contact details.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recipe&lt;/strong&gt; for a recipe page with ingredients and steps.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Use the type that fits the page you actually have. If no type fits well, do not force one. One relevant type per page is a good starting point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Match the markup to visible content
&lt;/h2&gt;

&lt;p&gt;This is the rule that matters most. Every important detail in your markup should also appear on the page itself, where a visitor can see it. Do not mark up reviews, prices, opening hours or answers that are hidden from visitors, and do not copy the same business or product markup onto unrelated pages.&lt;/p&gt;

&lt;p&gt;If a price changes, an answer changes, or a page is removed, update the markup as well. Outdated markup is worse than no markup, because it can confuse search engines and readers alike.&lt;/p&gt;

&lt;h2&gt;
  
  
  Generate JSON-LD without writing code
&lt;/h2&gt;

&lt;p&gt;You can generate the code with a free tool instead of writing JSON-LD by hand. For example, you can use the free Schema Markup Generator from Quicklity: &lt;a href="https://quicklitytools.com/schema-markup-generator" rel="noopener noreferrer"&gt;https://quicklitytools.com/schema-markup-generator&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A practical workflow is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Choose the schema type that matches your page.&lt;/li&gt;
&lt;li&gt;Fill in only the fields that match the visible content on that page.&lt;/li&gt;
&lt;li&gt;Copy the JSON-LD code the tool produces.&lt;/li&gt;
&lt;li&gt;Add it to your page. Many website builders, content management systems and SEO plugins let you paste code into a page header or a dedicated schema field, without editing theme files.&lt;/li&gt;
&lt;li&gt;Save the page and check that the content still reads naturally for visitors.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Test before you finish
&lt;/h2&gt;

&lt;p&gt;After adding markup, test the live page URL with Google's Rich Results Test. It will show whether the markup is valid and which enhancements, if any, the page may be eligible for. Fix errors it reports, such as missing required fields or invalid values, and retest after each change.&lt;/p&gt;

&lt;p&gt;A passing test is a useful check, not a promise. Search engines decide whether to show an enhanced result, and that decision can change over time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes to avoid
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Marking up content that visitors cannot see.&lt;/li&gt;
&lt;li&gt;Using FAQ markup for questions that are not answered on the page.&lt;/li&gt;
&lt;li&gt;Using a Product type for a page that is not a product page.&lt;/li&gt;
&lt;li&gt;Copying the same markup across every page of a site.&lt;/li&gt;
&lt;li&gt;Expecting a rich result just because the test passes.&lt;/li&gt;
&lt;li&gt;Adding markup once and never updating it when the page changes.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A simple starting plan
&lt;/h2&gt;

&lt;p&gt;Start with one important page, one correct type, and one test. When that feels comfortable, repeat the process for your next most important pages. Keep the markup accurate, visible and up to date, and let the content itself do the main work. That steady approach is far more useful than adding complex markup everywhere at once.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>seo</category>
    </item>
    <item>
      <title>GST Math Without the Headache: Exclusive vs Inclusive Prices, Explained</title>
      <dc:creator>Quicklity</dc:creator>
      <pubDate>Thu, 29 Oct 2026 05:16:15 +0000</pubDate>
      <link>https://dev.to/quicklitytools/gst-math-without-the-headache-exclusive-vs-inclusive-prices-explained-3fee</link>
      <guid>https://dev.to/quicklitytools/gst-math-without-the-headache-exclusive-vs-inclusive-prices-explained-3fee</guid>
      <description>&lt;p&gt;GST confusion usually comes down to one question: is the tax already inside the price, or added on top? Get that wrong and every invoice, quote, and profit margin is off.&lt;/p&gt;

&lt;h2&gt;
  
  
  Exclusive: tax added on top
&lt;/h2&gt;

&lt;p&gt;A GST-exclusive price does not include tax yet. Tax = price × GST rate, and the customer pays price + tax. Example: a product priced at 1,000 with 18% GST means 180 in tax, so the total is 1,180.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inclusive: tax already inside the price
&lt;/h2&gt;

&lt;p&gt;A GST-inclusive price already contains the tax. You cannot just take 18% of the total — that overstates the tax. Instead: base price = total ÷ (1 + GST rate), and tax = total − base price. Example: a total of 1,180 at 18% GST gives a base price of 1,180 ÷ 1.18 = 1,000, and tax of 180.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three mistakes to avoid
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Applying the rate directly to an inclusive price — this inflates the tax amount.&lt;/li&gt;
&lt;li&gt;Mixing rates across items on one invoice — calculate each line separately.&lt;/li&gt;
&lt;li&gt;Rounding too early — round only the final figures, not every intermediate step.
## When reverse calculation matters
Reverse (inclusive-to-exclusive) math is what you need when checking a supplier bill, breaking down a quoted total for an invoice, or working out your real margin on a tax-inclusive selling price.
## Do it instantly
The free GST Calculator at &lt;a href="https://quicklitytools.com/gst-calculator" rel="noopener noreferrer"&gt;https://quicklitytools.com/gst-calculator&lt;/a&gt; handles both modes — enter the amount and rate, switch between exclusive and inclusive, and get the tax and total straight away. No sign-up, it runs in your browser.&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>gst</category>
      <category>calculator</category>
      <category>finance</category>
      <category>business</category>
    </item>
    <item>
      <title>Stop Guessing Your UTMs: A Practical Guide to Clean Campaign Links</title>
      <dc:creator>Quicklity</dc:creator>
      <pubDate>Tue, 27 Oct 2026 03:27:47 +0000</pubDate>
      <link>https://dev.to/quicklitytools/stop-guessing-your-utms-a-practical-guide-to-clean-campaign-links-2b78</link>
      <guid>https://dev.to/quicklitytools/stop-guessing-your-utms-a-practical-guide-to-clean-campaign-links-2b78</guid>
      <description>&lt;p&gt;Campaign links fail quietly. A typo in utm_source, an inconsistent medium name, or a space in a campaign name can split one campaign into five different reports in Google Analytics — and you only notice weeks later, when the data is already messy.&lt;/p&gt;

&lt;p&gt;This guide covers a simple, repeatable way to build UTM links that stay clean, plus the mistakes I see most often.&lt;/p&gt;

&lt;h2&gt;
  
  
  What each UTM parameter actually does
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;utm_source: where the traffic comes from, e.g. google, newsletter, instagram.&lt;/li&gt;
&lt;li&gt;utm_medium: the type of traffic, e.g. cpc, email, social, referral.&lt;/li&gt;
&lt;li&gt;utm_campaign: the name of the campaign, e.g. spring_sale_2026.&lt;/li&gt;
&lt;li&gt;utm_term and utm_content: optional, useful for paid keywords and for telling apart two links in the same email or ad set.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You do not need all five on every link. Source, medium, and campaign are the core trio. Add term and content only when they genuinely help you compare things.&lt;/p&gt;

&lt;h2&gt;
  
  
  A naming rule that saves you later
&lt;/h2&gt;

&lt;p&gt;Pick lowercase, no spaces, and one separator, then stick to it. For example: use underscores inside names (spring_sale) and keep a short list of allowed sources and mediums. If one person writes "Facebook", another writes "facebook", and a third writes "fb", Analytics treats them as three different sources.&lt;/p&gt;

&lt;p&gt;Write your convention down somewhere your whole team can see it. A shared doc with ten lines beats a perfect system nobody follows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build the link in the right order
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Start with the final landing page URL, including any existing path — do not add UTMs to a redirect or a shortened link you cannot control.&lt;/li&gt;
&lt;li&gt;Add source, medium, and campaign.&lt;/li&gt;
&lt;li&gt;Add term or content only if you need them.&lt;/li&gt;
&lt;li&gt;Check the full URL before you copy it: one stray ampersand or unencoded character can break the whole string.&lt;/li&gt;
&lt;li&gt;Test it once in a browser and confirm the landing page loads and the parameters stay intact.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A free browser tool can handle the encoding and ordering for you. Quicklity's UTM Builder (&lt;a href="https://quicklitytools.com/utm-builder" rel="noopener noreferrer"&gt;https://quicklitytools.com/utm-builder&lt;/a&gt;) builds the link from your inputs and keeps the format consistent, which removes the most common copy-paste errors.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistakes that quietly ruin UTM data
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Using UTMs on internal links. They overwrite the original source, so do not tag links inside your own site.&lt;/li&gt;
&lt;li&gt;Changing naming mid-campaign. A rename halfway through splits your reporting in two.&lt;/li&gt;
&lt;li&gt;Tagging every link differently "just in case". Extra parameters do not add insight; they add noise.&lt;/li&gt;
&lt;li&gt;Forgetting to check the link after shortening it. Some shorteners strip parameters unless you configure them not to.&lt;/li&gt;
&lt;li&gt;Using spaces or capital letters inconsistently. Both create duplicate rows in reports.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A quick checklist before you share any UTM link
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Lowercase source, medium, and campaign?&lt;/li&gt;
&lt;li&gt;No spaces, one separator style?&lt;/li&gt;
&lt;li&gt;Landing page correct and loading?&lt;/li&gt;
&lt;li&gt;Parameters still present after any shortener?&lt;/li&gt;
&lt;li&gt;Same naming as the rest of the campaign?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If all five are yes, share it. If not, fix it now — it takes seconds today and saves hours of report cleanup later.&lt;/p&gt;

&lt;p&gt;Clean UTMs are not about being fancy. They are about being consistent, so that when a campaign works, you can actually prove which channel, post, or email did the work.&lt;/p&gt;

</description>
      <category>utm</category>
      <category>analytics</category>
      <category>marketing</category>
      <category>seo</category>
    </item>
  </channel>
</rss>
