Remote SEO Consultant | Entity SEO Lessons From a Real Rebrand
Remote SEO Consultant rebranded from Istiqur IT Consultant. A developer's breakdown of entity resolution, schema.org, and why a name is basically an identifier.
I rebranded my SEO consulting practice from Istiqur IT Consultant to Remote SEO Consultant. Here's the entity-SEO breakdown — with actual schema.org markup — of why a name is basically an identifier, and what breaks when it doesn't match the query.
- Md. Istiqur Rahman, Remote SEO Consultant (SaaS & eCommerce) / Remote GTM Manager (Solopreneurs & Entrepreneurs)
Remote SEO Consultant is the new name and domain (remoteseoconsultant.com) for 18 years of work formerly published under Istiqur IT Consultant. The rename wasn't cosmetic — it was fixing a broken entity identifier, and the fix generalizes to any service business shipping structured data.
TL;DR
- Renamed Istiqur IT Consultant → Remote SEO Consultant (RSC), new domain remoteseoconsultant.com
- The real problem: my old name wasn't a working identifier for the entity search engines and LLMs needed to resolve
- Includes a working
schema.orgJSON-LD pattern (Person+ProfessionalService,alternateName,sameAs) you can adapt for your own rebrand or personal-brand site - Same operator, same 18-year track record, same three services — only the label and the markup changed
- istiquritconsultant.com isn't gone — it's becoming my personal tech diary, unrelated to client work
Names Are Identifiers. Mine Wasn't Resolving.
If you've ever debugged a system where two records that should be the same entity don't match because of an inconsistent key, you already understand the problem I had with my own business name.
For 18 years I ran a consulting practice under Istiqur IT Consultant. Technically accurate — that's my name, and I do consult on technical things. But as an identifier for the entity search engines and AI systems were trying to resolve — "who does SEO for SaaS and eCommerce companies" — it was a broken key. It pointed to a person, not a category. Nobody queries a stranger's name when they have an SEO problem; they query the problem. My old name simply didn't match the query space it needed to match.
A name is an identifier — mine had a resolution bug.
So I renamed the entity: Remote SEO Consultant (RSC), at remoteseoconsultant.com. Same person, same 18 years of hands-on organic and technical SEO plus AI/LLM search optimization (AEO, GEO), same small expert remote team. The identifier changed. The entity behind it didn't.
Why This Is an Entity-Resolution Problem, Not a Branding Problem
Modern search — both classic Google indexing and the newer generation of LLM-driven answer engines — doesn't just match strings, it tries to resolve entities: is this website, this name, and this set of claims all describing the same real-world thing? That resolution gets easier when four things are true:
- The name contains the category. Searchable beats personal, for a service business.
-
Structured data explicitly declares who's who.
schema.orgtypes likePerson,ProfessionalService, andOrganizationaren't decoration — they're the machine-readable version of your positioning. -
alternateNamecovers the old identity. A rebrand doesn't erase prior mentions, backlinks, or citations. You want the graph to know your old name and new name are the same node. -
sameAsties every profile back to one canonical identity. No drift between what one platform claims and what another does.
My old name failed the first bullet outright, which made the other three do more work than they should have had to.
The Actual Markup
This is the real pattern I shipped on the new domain — trimmed to the parts that matter for the entity-identity problem specifically:
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Md. Istiqur Rahman",
"url": "https://remoteseoconsultant.com/istiqur-it-consultant/",
"jobTitle": "Remote SEO Consultant",
"worksFor": { "@id": "https://remoteseoconsultant.com/#organization" },
"sameAs": [
"https://www.linkedin.com/in/md-istiqur-rahman-rabby/",
"https://x.com/mdistiqurrahman",
"https://www.facebook.com/remoteseoconsultant",
"https://www.instagram.com/remoteseoconsultant"
]
}
{
"@context": "https://schema.org",
"@type": "ProfessionalService",
"name": "Remote SEO Consultant",
"alternateName": ["RSC", "Istiqur IT Consultant"],
"url": "https://remoteseoconsultant.com",
"founder": { "@id": "https://remoteseoconsultant.com/istiqur-it-consultant/#person" }
}
Two things worth calling out if you're adapting this for your own rebrand:
-
alternateNameis doing the entity-continuity work. Without it, a search engine (or an LLM doing retrieval) has no explicit signal that "Istiqur IT Consultant" and "Remote SEO Consultant" are the same entity across historical mentions and new content. You're not hiding the old name — you're telling the graph it's the same node. -
sameAsis only useful if it's exhaustive and consistent. A partial list, or profiles with drifting bio text, actively works against you — it reads as weaker identity signal than having nosameAsat all in some cases, because it invites the resolver to treat the profiles as only loosely related.
The Logomark Is Basically a Literal Diagram of This
This part genuinely amused me once I saw it drawn out. The new logomark is called Ascent — a violet hub node linked to three satellite nodes, the largest pushed asymmetrically to the upper right. It's built to read as a small knowledge graph: a hub entity connected to related entities, exactly the structure a search engine or LLM builds internally when it resolves who you are. The hub is the consultant; the satellites are the distributed collaborators — a remote team with a lead, encoded as a graph shape before you even read the wordmark.
The wordmark sets "REMOTE" small and widely tracked above a dominant, bold "SEO Consultant" — the exact-match category term gets the visual weight, while the whole lockup still reads as one name. Palette: #6F2DBD primary, #A663CC secondary, #171123 ink, #FBFBFB paper. Headings in Bricolage Grotesque, body in Inter.
The mark is basically a knowledge graph diagram.
What Actually Changed vs. What's a No-Op
Changed (the identifier layer):
- Name: Istiqur IT Consultant → Remote SEO Consultant (RSC)
- Domain: istiquritconsultant.com → remoteseoconsultant.com
- Structured data across every page, adding
alternateNameand a completesameAsgraph - Positioning copy across every channel, to stop describing a person and start describing a category
Unchanged (the entity underneath):
- The operator — still me, on every engagement, no hand-off to a junior account manager
- The team — small and expert, not a large agency
- 18+ years of hands-on SEO/GTM work across nine countries: USA, Mexico, UK, Saudi Arabia, Pakistan, India, Bangladesh, New Zealand, Australia
- Three services: SEO for SaaS, SEO for eCommerce, and web development for small business (full list on the services archive)
- Real outcomes carried forward: 150K+ monthly users for a Silicon Valley SaaS startup, 14K+ monthly enterprise users for a Californian AI startup, $284K+/month for a USA cosmetics eCommerce brand, 4.81/5 average client rating
If You're Doing This Yourself
A short checklist, for any dev handling a rebrand or a personal-brand site's structured data — deliberately generic, not a specific implementation writeup:
- Pick
PersonvsOrganization/ProfessionalServicebased on who the entity actually is — don't default toOrganizationjust because it sounds more official. - Populate
alternateNamewith every prior name your entity has been publicly known by. Skip it and you're asking the resolver to start from zero. - Keep
sameAsexhaustive and keep the linked profiles' bio text consistent with your canonical claims — inconsistency is worse than a short list. - Match your on-page copy to the same category language your structured data claims. Markup that says "SEO Consultant" while your H1 says "IT Consultant" is a contradiction, not a nuance.
- Re-crawl and re-submit affected URLs after the change — structured data updates don't propagate instantly.
Who This Is Actually Useful To
If you're a developer who also touches technical SEO — or you're a solopreneur/SaaS founder trying to figure out why your own service business isn't showing up for the exact thing you do — the lesson generalizes: a name that isn't a working identifier for your category is a tax on every discovery channel you have, not just organic search. Fix the identifier before you fix the funnel.
If you want the practitioner side of that (not just the theory), Remote SEO Consultant is built for solopreneurs, entrepreneurs, SaaS founders and co-founders, marketing/product leads, and eCommerce owners who want a senior operator directly on their SEO and GTM — not a junior account manager relaying instructions.
How to Engage
- Book a free strategy call
- See every service
- Get free growth tips (newsletter)
- About me
- Full site map
istiquritconsultant.com, for the record, isn't dead — it's becoming my personal tech diary, separate from client-facing work.
FAQ
Why did Istiqur IT Consultant rebrand to Remote SEO Consultant?
The old name described a person, not a problem solved. Remote SEO Consultant states the actual value — SEO and GTM leadership for SaaS and eCommerce — in searchable, specific language.
Is this a new company, or the same person and services under a new name?
Same person, same team, same 18 years of work — Md. Istiqur Rahman, operating personally on every account. Only the name, domain, and positioning changed.
What happened to istiquritconsultant.com?
It's being converted into a personal tech diary, separate from client-facing service content, which now lives entirely at remoteseoconsultant.com.
What services does Remote SEO Consultant actually offer?
SEO for SaaS, SEO for eCommerce, and web development (WordPress/Webflow) for startups and small businesses — full detail on the services archive page.
Who is Remote SEO Consultant the right fit for?
Solopreneurs, entrepreneurs, SaaS founders, marketing/product leaders, and eCommerce owners who want a senior operator directly on their SEO and GTM, not a junior account manager.
Fixing a broken identifier — the full diff.
AUTHOR BIO
Md. Istiqur Rahman — Remote SEO Consultant (SaaS & eCommerce) / Remote GTM Manager (Solopreneurs & Entrepreneurs) / WordPress & Webflow Developer for Startups & Online Stores. Practicing SEO and full-stack marketing since 2008 with an M-shaped skillset across Organic SEO, LLM Search & AI Optimization (AI SEO, AIO, AEO), and Generative Engine Optimization (GEO). A-grade post-graduate pharmacist by academic background.
