DEV Community: Quicklity

Schema Markup Without Code: A Beginner's Guide to Rich Results

Quicklity — Mon, 02 Nov 2026 02:04:31 +0000

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.

What schema markup actually is

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.

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.

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.

Pick the right type first

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

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

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.

Match the markup to visible content

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.

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.

Generate JSON-LD without writing code

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: https://quicklitytools.com/schema-markup-generator

A practical workflow is:

Choose the schema type that matches your page.
Fill in only the fields that match the visible content on that page.
Copy the JSON-LD code the tool produces.
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.
Save the page and check that the content still reads naturally for visitors.

Test before you finish

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.

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.

Common mistakes to avoid

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

A simple starting plan

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.

GST Math Without the Headache: Exclusive vs Inclusive Prices, Explained

Quicklity — Thu, 29 Oct 2026 05:16:15 +0000

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.

Exclusive: tax added on top

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.

Inclusive: tax already inside the price

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.

Three mistakes to avoid

Applying the rate directly to an inclusive price — this inflates the tax amount.
Mixing rates across items on one invoice — calculate each line separately.
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 https://quicklitytools.com/gst-calculator 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.

Stop Guessing Your UTMs: A Practical Guide to Clean Campaign Links

Quicklity — Tue, 27 Oct 2026 03:27:47 +0000

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.

This guide covers a simple, repeatable way to build UTM links that stay clean, plus the mistakes I see most often.

What each UTM parameter actually does

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

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.

A naming rule that saves you later

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.

Write your convention down somewhere your whole team can see it. A shared doc with ten lines beats a perfect system nobody follows.

Build the link in the right order

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.
Add source, medium, and campaign.
Add term or content only if you need them.
Check the full URL before you copy it: one stray ampersand or unencoded character can break the whole string.
Test it once in a browser and confirm the landing page loads and the parameters stay intact.

A free browser tool can handle the encoding and ordering for you. Quicklity's UTM Builder (https://quicklitytools.com/utm-builder) builds the link from your inputs and keeps the format consistent, which removes the most common copy-paste errors.

Mistakes that quietly ruin UTM data

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

A quick checklist before you share any UTM link

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

If all five are yes, share it. If not, fix it now — it takes seconds today and saves hours of report cleanup later.

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.