<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Asad Bukhari]]></title><description><![CDATA[Asad Bukhari]]></description><link>https://asad-bukhari.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Mon, 16 Nov 2026 18:47:07 GMT</lastBuildDate><atom:link href="https://asad-bukhari.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Google Business Profile: The 10-Minute Setup Checklist for a Local Business]]></title><description><![CDATA[A local business without a Google Business Profile is invisible in the place its customers actually search: Google Maps and the local results on Google…]]></description><link>https://asad-bukhari.hashnode.dev/google-business-profile-the-10-minute-setup-checklist-for-a-local-business</link><guid isPermaLink="true">https://asad-bukhari.hashnode.dev/google-business-profile-the-10-minute-setup-checklist-for-a-local-business</guid><category><![CDATA[SEO]]></category><category><![CDATA[google business profile]]></category><category><![CDATA[local seo]]></category><category><![CDATA[webdev]]></category><dc:creator><![CDATA[Asad Bukhari]]></dc:creator><pubDate>Sun, 15 Nov 2026 09:46:19 GMT</pubDate><content:encoded><![CDATA[<p>A local business without a Google Business Profile is invisible in the place its customers actually search: Google Maps and the local results on Google Search. Setting one up properly takes about ten minutes of focused work, and it is one of the highest-value jobs a small business can do for itself. This is the checklist I use.</p>
<h2>1. Claim the profile, or create it</h2>
<p>Search for the business name on Google Maps. If a profile already exists, claim it. If not, create one. One profile per real location — a business with one shop gets one profile, not one per service.</p>
<h2>2. Make the name, address, and phone number match everywhere</h2>
<p>The business name, address, and phone number must be exactly the same on the profile, on the website, and on every listing. "Street 5, Main Bazaar" on the website and "St 5 Main Bazar" on the profile is a mismatch. Pick one spelling and use it everywhere. This is the single most common mistake I see, and it takes seconds to fix.</p>
<h2>3. Pick the right primary category</h2>
<p>The primary category decides which searches the business appears for. A salon should be "Beauty Salon" or "Hair Salon", not "Spa" if it does not offer spa services. Be specific: the right category brings the right customers, and the wrong one brings people who leave disappointed.</p>
<h2>4. Set the real working hours</h2>
<p>Set the hours the business is actually open, including different hours for different days. If Friday hours differ, set Friday separately. And update the hours for public holidays — a customer who drives to a closed shop because the profile said "Open" will not come back.</p>
<h2>5. Add the website and the booking link</h2>
<p>Add the business website in the website field, and the booking or WhatsApp link where Google allows it. A profile without a website link is a dead end: the customer found you, and has nowhere to go next.</p>
<h2>6. Add real photos, not stock photos</h2>
<p>Add photos of the real shop, the real staff, and real work. Customers trust a photo of the actual place far more than a stock image. A few honest photos — the entrance, the inside, one or two examples of the work — are enough to start. Add more over time, and keep them current.</p>
<h2>7. Write a short, honest description</h2>
<p>The description should say what the business does, who it is for, and where it is — in plain words. It is not a place for keyword stuffing. A customer reading it should know within two lines whether this is the business they need.</p>
<h2>8. Ask for reviews, and reply to them</h2>
<p>After a happy customer leaves, ask them to leave a review on the profile. One honest review is worth more than a dozen claims on the website. And reply to every review, good or bad — a short, human reply shows the next customer that the business is listening.</p>
<h2>9. Post once a week</h2>
<p>A short post once a week — a new service, an offer, a photo of recent work — keeps the profile alive. It takes five minutes and it signals to Google and to customers that the business is active.</p>
<h2>10. Check it every month</h2>
<p>Once a month, open the profile as a customer would: check the hours, the phone number, the photos, and the reviews. Details change, and a profile that is not checked slowly goes out of date. Ten minutes a month keeps it accurate.</p>
<hr />
<p>That is the whole setup. Ten steps, ten minutes to start, and a short monthly check after that. A complete, accurate profile does not guarantee the top spot in local results — nothing does — but a business without one is not even in the race.</p>
<h2>Author Bio</h2>
<p>Muhammad Asad Bukhari is a freelance WordPress developer based in Lahore, Pakistan. He builds WordPress websites for small and service businesses, including salons and spas, sets up AI automation with n8n workflows, and manages Google Business Profiles for local businesses. His portfolio is at <a href="https://asadbukhari.site">https://asadbukhari.site</a>.</p>
]]></content:encoded></item><item><title><![CDATA[A 6-Page WordPress Site, One SEO Plugin, and a Full Title-and-Heading Pass: What I Actually Fixed]]></title><description><![CDATA[A small service business came to me with a WordPress website that looked finished. It had pages, it had text, and it loaded. The problem was not the…]]></description><link>https://asad-bukhari.hashnode.dev/a-6-page-wordpress-site-one-seo-plugin-and-a-full-title-and-heading-pass-what-i-actually-fixed</link><guid isPermaLink="true">https://asad-bukhari.hashnode.dev/a-6-page-wordpress-site-one-seo-plugin-and-a-full-title-and-heading-pass-what-i-actually-fixed</guid><category><![CDATA[WordPress]]></category><category><![CDATA[SEO]]></category><category><![CDATA[webdev]]></category><dc:creator><![CDATA[Asad Bukhari]]></dc:creator><pubDate>Sun, 15 Nov 2026 09:40:57 GMT</pubDate><content:encoded><![CDATA[<p>A small service business came to me with a WordPress website that looked finished. It had pages, it had text, and it loaded. The problem was not the design. The problem was that the basic SEO work had never been done properly. Page titles were not doing their job. Meta descriptions were missing or unhelpful. Headings did not give search engines — or visitors — a clear idea of what each page was about.</p>
<p>I fixed that in one focused pass. I did not rebuild the site or change the design. I worked through the live pages one by one, fixed the titles and meta descriptions, fixed the headings, and checked that the contact details matched the details the owner had confirmed.</p>
<p>This article is a record of that pass, for anyone who runs a small WordPress site, or looks after one for a client, and wants to do the same job in a day. There are no shortcuts in it, and no claims I cannot support. What follows is the order I worked in, the checks I used, and the mistakes I made sure not to repeat.</p>
<p>The site is a landscaping business website with six live pages. I will not name the business, and I will not share its contact details. The lessons do not depend on the name. They depend on the structure, and that structure is the same on most small service-business sites.</p>
<h2>Start with the live site, not with the plugin</h2>
<p>The first step was to look at the live site as a visitor would see it. I opened each of the six pages in turn and wrote down the page title in the browser tab, the heading at the top of the page, and where the contact details appeared — and whether they said the same thing on every page.</p>
<p>That list became my working document for the whole job. It told me what was missing before I opened any settings screen. That matters, because it is easy to spend a long time inside a plugin and forget to check what the visitor actually sees.</p>
<p>I also resisted the urge to start by changing plugins. The site already had an SEO plugin installed. It was SureRank, not Rank Math. That is worth saying plainly, because most WordPress SEO advice assumes Rank Math or one of the other well-known plugins. The work is the same — a title, a meta description, and a heading for each page — but the tool I used was the tool that was already there.</p>
<p>There is a practical reason for that. Switching plugins in the middle of a small fix creates new work: exporting settings, learning a new screen, and checking that nothing was lost in the move. On a six-page site, that work is larger than the fix itself. If the installed plugin can set a title, a meta description, and a heading structure, it is good enough for the job.</p>
<h2>Step 1: Give every page a title that says what the page is</h2>
<p>A page title is the text that appears in the browser tab and in search results. It is also one of the first things a visitor reads when they find the site through a search.</p>
<p>Before the fix, the titles on this site were not doing that job. Some were vague. Some repeated the same words across different pages, so two pages looked like the same page in search results. A visitor could not tell from the title which service a page was about.</p>
<p>I wrote a new title for each of the six pages, one page at a time. I used the same rules for all six:</p>
<p><strong>Name the page's subject first.</strong> A service page should start with the service it describes, not with the business name.</p>
<p><strong>Use the business name once, at the end.</strong> It belongs in the title, but it is not the most useful word for a new visitor.</p>
<p><strong>Make each title different.</strong> If two pages have the same title, they look like duplicates. I checked all six titles side by side before I saved them.</p>
<p><strong>Write for the person reading the search result.</strong> A title is not a list of keywords. It is a short sentence a person reads before deciding whether to click.</p>
<p>I did not try to make the titles clever. On a service-business site, clear beats clever. The visitor wants to know whether this page is the service they need. The title should answer that in one line.</p>
<p>After writing all six titles, I saved them and opened each live page again to check them. A title can look right in the plugin field and still be wrong on the live page — for example, if the site adds the business name automatically and the result repeats it. I checked the browser tab for each page and fixed any title that came out doubled or cut off.</p>
<h2>Step 2: Write a meta description for every page, not just the homepage</h2>
<p>A meta description is the short text that can appear under a page title in search results. It does not decide where a page ranks, but it does help a person decide whether to click. A page with no meta description leaves that text to chance: a search engine will pick a piece of text from the page, and it may pick the wrong piece — a line from a footer or a navigation label.</p>
<p>On this site, the meta descriptions had the same problem as the titles: they were missing or unhelpful on pages other than the homepage. The homepage had received the attention. The service pages had not. That is a common pattern on small sites. I wrote a meta description for all six pages, using the same rules as the titles:</p>
<p><strong>Describe what the visitor will find on this page.</strong> A service page should say what the service is and who it is for. A contact page should say how to get in touch.</p>
<p><strong>Make each description different.</strong> A copied description across pages tells the reader nothing about which page they are looking at. I wrote each one from the content of its own page, and checked all six side by side.</p>
<p><strong>Do not repeat the title word for word.</strong> The title and the description appear together in search results. Use the description to add something the title does not say.</p>
<p><strong>Keep it honest.</strong> A description should not promise something the page does not offer. Visitors notice when the description and the page do not match, and they leave.</p>
<p>I kept the descriptions short and plain. Long descriptions get cut off in search results. A short description that fits is better than a long one that ends halfway through a sentence. I read each one aloud before saving it. If it sounded like a sentence a person would say, I kept it.</p>
<h2>Step 3: Fix the headings — one H1 per page, and no skipping</h2>
<p>Headings are the structure of a page. The main heading, the H1, tells the reader what the page is about. The headings below it break the page into sections. When the headings are right, a visitor can scan a page and understand it in seconds.</p>
<p>Before the fix, the headings on this site were inconsistent. Some pages had more than one main heading. Some had a main heading that did not match the subject of the page. The problem is easy to create on WordPress, because headings come from more than one place: the page title, the theme, and the blocks inside the page content. A page can end up with two H1s without anyone noticing, because each one looks correct on its own.</p>
<p>I checked the headings on each of the six pages and fixed them to a simple rule: <strong>one H1 per page, and it should name the subject of that page.</strong> The headings below it should follow in order, without skipping a level, and each one should describe the section that follows it. A heading should not be used to make text look larger or bolder.</p>
<p>Here is the check I used on each page, and it is the same check a reader can use on their own site: read the first heading — does it say what the page is about? Count the H1s — there should be one, and if there are two, work out where the second comes from, often the page title added by the theme or a heading block set to H1 by mistake, and change one to the next level down. Read the rest of the headings in order — do they describe the sections below them? And look for skipped levels, which make a page harder to follow.</p>
<p>This is slow work, because it means reading each page rather than scanning a settings screen. But it is the part of the job that most affects how a visitor experiences the site.</p>
<h2>Step 4: Make the contact details say the same thing everywhere</h2>
<p>A service business website exists so that a visitor can get in touch. If the contact details are wrong, out of date, or different on different pages, the site fails at its main job — even if the titles and headings are perfect.</p>
<p>On this site, the owner had confirmed the correct contact details. I used those confirmed details as the single source of truth, checking where they appeared on the site and making sure they matched. I did not add contact details from memory, and I did not copy them from an old listing or an old message. When the owner is the source, the owner is the source. Anything else is a guess.</p>
<p>That rule sounds obvious, but it is the one most often broken on small sites. Contact details change, and the site is updated in one place and not in another. After a while, the site disagrees with itself. The visitor cannot tell which version is right, and some visitors will simply give up rather than risk calling the wrong number.</p>
<p>The check is simple, and it is worth doing on any small site: write down the confirmed contact details in one place; open every page that shows them and compare it with that list; fix any page that differs, even if the difference looks small; and do the same for the footer and any contact section that appears on more than one page, because those are the places where an old version survives longest.</p>
<p>I am not sharing the contact details for this business in this article. The point is the method, not the details: one confirmed source, checked on every page.</p>
<h2>What I deliberately did not do</h2>
<p>It is worth saying what this pass did not include, because the things I left out are as important as the things I did.</p>
<p>I did not invent results. I am not claiming in this article that the site's traffic or rankings changed by any amount, because I did not measure a change and I do not have verified numbers to share. A title-and-heading pass is basic work. It is worth doing. But basic work does not justify a results claim. If you read an article that describes a small on-page fix and then reports a large improvement, ask what was measured, over what period, and what else changed at the same time. If the article cannot answer those questions, treat the improvement as unproven.</p>
<p>I did not add pages the business did not need — six live pages were enough — and I did not stuff the titles and descriptions with extra words in the hope of covering more searches. A title that tries to say everything says nothing clearly. And I did not treat the plugin as the work. SureRank was the tool I used to enter the titles and descriptions. The work was deciding what those titles and descriptions should say. A different plugin would have needed the same decisions.</p>
<h2>Making the pass repeatable</h2>
<p>The value of this job is not only that one site is now in better order. It is that the same pass can be repeated on another small site without starting from scratch. The steps are the same every time, and they fit on a single checklist: open every live page and note the title, main heading, and contact details; write a new title for each page, subject first and business name at the end, each one different; write a meta description for each page from its own content, without repeating the title; fix the headings — one H1 per page, in order, each describing the section below it; check the contact details against one confirmed source on every page where they appear; and open each live page again to check the result, rather than trusting the settings screen alone.</p>
<p>In my wider work, I also set up AI automation with n8n workflows for small businesses, and the same idea applies there: write down the steps, make them repeatable, and check the result on the live system rather than trusting a settings screen. Automation does not replace the checks in this article. Automate the reminders and the record-keeping around it, not the judgement about what a title should say.</p>
<p>For a reader who wants to do this today, the first step is the smallest one: open your own site, pick one page, and read its title, its meta description, and its headings as a visitor would. If any of them is vague, repeated from another page, or wrong, you have found your first fix. Do that page, then do the next one. A six-page site can be worked through in a single focused session.</p>
<p>That is the whole job. It is not glamorous, and it does not need a new tool. It needs a list, a careful read of each page, and the discipline to check the live site after saving.</p>
<h2>Author bio</h2>
<p>Muhammad Asad Bukhari is a freelance WordPress developer based in Lahore, Pakistan. He builds WordPress websites for small and service businesses, including salons and spas, sets up AI automation with n8n workflows, and works on SEO for WordPress sites. His portfolio is at <a href="https://asadbukhari.site">https://asadbukhari.site</a>.</p>
]]></content:encoded></item><item><title><![CDATA[One n8n workflow that saves a small business an hour a day]]></title><description><![CDATA[Small businesses rarely lose enquiries because their website is broken. They lose them because follow-up is manual, and manual work gets interrupted. A new…]]></description><link>https://asad-bukhari.hashnode.dev/one-n8n-workflow-that-saves-a-small-business-an-hour-a-day</link><guid isPermaLink="true">https://asad-bukhari.hashnode.dev/one-n8n-workflow-that-saves-a-small-business-an-hour-a-day</guid><category><![CDATA[n8n]]></category><category><![CDATA[WordPress]]></category><category><![CDATA[automation]]></category><category><![CDATA[webdev]]></category><dc:creator><![CDATA[Asad Bukhari]]></dc:creator><pubDate>Sun, 15 Nov 2026 05:18:25 GMT</pubDate><content:encoded><![CDATA[<p>Small businesses rarely lose enquiries because their website is broken. They lose them because follow-up is manual, and manual work gets interrupted. A new enquiry arrives, someone means to reply, then a customer walks in or the working day ends — and the enquirer may already have contacted another business by the time the reply is sent.</p>
<p>This post walks through one n8n workflow built for that task: following up new website enquiries. It covers the manual process, the workflow, and what to check before relying on it. It claims no measured result. No time saving was measured for this workflow, and no result is stated as a fact.</p>
<h2>The task: following up new website enquiries</h2>
<p>The task is the follow-up after a new enquiry arrives from a website contact form. It fits automation because it is repetitive, follows a clear pattern, and matters every time.</p>
<p>Every enquiry needs the same handling: the business needs to know it arrived, who sent it, and what they asked for, and the enquirer needs a prompt acknowledgement. The problem is not difficulty. It is that this has to happen every time, even on busy days. A task that is easy once becomes fragile when it must be done reliably, by hand, again and again.</p>
<h2>How it works now: the manual steps</h2>
<p>Before building anything, write down the manual process exactly as it happens. Unclear manual steps make an unclear automated version.</p>
<p>A visitor fills in the contact form on the WordPress website. The enquiry arrives as an email, or as a form entry in the WordPress dashboard. Then someone has to notice it, by checking email or the dashboard. If no one checks, the enquiry waits.</p>
<p>Next, someone reads it and decides what it is about: a general question, a request for prices, or a request to book. That shapes the reply, usually typed from scratch or copied from an old message and edited. Then someone has to remember to follow up if there is no reply — the step most often missed, with no reminder unless someone creates one. Finally, someone records what happened, so the business knows which enquiries were answered and which are still waiting.</p>
<p>None of these steps is difficult alone. Together, they depend on attention, memory, and timing — which is why the same enquiry can be answered quickly one day and missed the next.</p>
<h2>Building the workflow</h2>
<p>The workflow was built in n8n around those manual steps, following the same logic in the same order.</p>
<p>The trigger is a new enquiry submitted through the website contact form. Nothing runs until one arrives, and every enquiry starts its own run, carrying the name, contact details, and message from the form. The first step records it in one place — a single list of everything that has come in. Without that record, there is no reliable way to tell a missed enquiry from an answered one.</p>
<p>The next step sorts the enquiry by what it is about. A general question, a request for prices, and a request to book are handled differently. If the message fits no expected kind, it goes to a general pile for a person to review, rather than receiving a mismatched reply.</p>
<p>Once recorded and sorted, the workflow sends a prompt acknowledgement, in short, plain wording: receipt confirmed, someone will reply. It promises no reply time and claims nothing unconfirmed. At the same time, it notifies the business — who sent it, what they asked for, and where the full message can be read.</p>
<p>The final step creates a follow-up reminder for enquiries with no full reply yet, attached to the record so the business can see what is still waiting. This guards against the most common manual failure: an enquiry acknowledged but never followed up. The workflow does not write the full reply. It keeps the enquiry visible until a person deals with it.</p>
<p>A workflow that only works when everything goes well is not ready to rely on. If a field is empty, the enquiry is still recorded and the missing detail flagged. If the same person submits twice, each submission is recorded separately. If the acknowledgement cannot be sent, the failure is recorded and the business notified. If the workflow stops, the form still collects enquiries as usual.</p>
<h2>Before and after</h2>
<p>Before, the process depended on checking, remembering, and recording by hand. An enquiry waited until someone noticed it, received a reply written from scratch, and was followed up only if someone remembered. There was no single list of what was waiting.</p>
<p>After, the process has a fixed order: record, sort, acknowledge, notify, and keep on a follow-up list until a person deals with it. The full reply is still written by a person; only the structure around it changed, so nothing waits on memory alone.</p>
<p>The work did not disappear. The reply still needs a person, and the follow-up still needs a decision. The routine parts — recording, sorting, acknowledging, notifying, and reminding — now happen the same way every time.</p>
<h2>What to check before relying on it</h2>
<p>Check the form fields first. The workflow can only work with the details the form collects, so a missing or wrongly optional field means more empty values to handle.</p>
<p>Check the acknowledgement wording as the enquirer would read it: clear, polite, and honest about what happens next, promising nothing the business cannot deliver.</p>
<p>Check where the record lives and who can see it — it is only useful if the people who answer enquiries can reach it. Check the notification reaches the right person, and that an enquiry stays on the follow-up list until answered.</p>
<p>Test it with a real submission before relying on it: submit an enquiry yourself and check it is recorded, the acknowledgement arrives, the notification arrives, and the reminder appears. Then test an empty field, a second submission, and a message that fits no expected kind.</p>
<p>Finally, agree on who answers the enquiries. Automation can record, sort, acknowledge, and remind, but it cannot decide what a business should say to a real person.</p>
<p>This workflow does not replace the person who answers enquiries. It replaces the parts that should not depend on memory: recording what arrived, acknowledging it promptly, letting the business know, and keeping it visible until answered. If your enquiries arrive through a website form, start by writing down your manual steps as they happen today. That list is the specification. Build around it and test with real submissions before you rely on it.</p>
<p>You can see more of my WordPress and automation work at <a href="https://asadbukhari.site">https://asadbukhari.site</a></p>
<h2>About the author</h2>
<p>Asad Bukhari is a freelance WordPress developer based in Lahore, Pakistan, working on WordPress websites, AI automation with n8n workflows, and SEO. Portfolio: <a href="https://asadbukhari.site">https://asadbukhari.site</a></p>
]]></content:encoded></item></channel></rss>