Discipline 04 — AI & Automation
The repetitive work becomes a tool.
Python tools calling SERP, DataForSEO and OpenAI APIs: keyword clustering, entity research, image metadata, structured data. Each one removes a manual step from SEO delivery — and each one stops before the judgement call.
- Primary stack
- Python · Streamlit · OpenAI API
- Data sources
- SERP APIs · DataForSEO · Google Autocomplete
- Built for
- Clustering, entities, metadata, schema
- Principle
- Automate volume, keep the judgement
-
6
Tools built
3 public repos · 3 internal
-
3
APIs in the loop
SERP · DataForSEO · OpenAI
-
1
Rule
Human check before publish
-
10+
Topical maps fed
Research to owning page
What I have built.
Three public repositories and three internal tools. Each entry says what it replaces, because a tool that saves nothing is a hobby.
-
SEO Clustering Tool
Keyword clustering through SERP URL overlap, with cost-aware caching that reduces DataForSEO and SERP API spend on large keyword sets.
-
Keyword Autocomplete Tool
Long-tail keyword discovery at scale using Google Autocomplete and the DataForSEO API, built to shorten research cycles.
-
Entity Intelligence Suite
Entity gathering, entity SEO research and competitor intelligence to support semantic SEO and topical-authority analysis.
-
Internal Links Checker
Audits supplied pages, classifies internal and external anchors, checks HTTP status and exports a four-column CSV for broken-link and orphan-page cleanup.
-
Image Metadata Processor
Produces lossless WebP copies and writes SEO filenames, alt text, XMP/EXIF/IPTC and GPS metadata at scale, with read-back verification.
-
JSON-LD Schema Generator
Generates paste-ready structured data for organisation, local business, service, article, how-to, FAQ, breadcrumb and person schema.
Judgement calls, not the structure.
AI is used where the volume is high and the answer is fuzzy. It is not used to decide what the site should say.
-
Research that a script cannot do alone
SERP-overlap clustering and entity extraction run on data APIs. The model handles the calls that need judgement — intent, ambiguity, near-duplicates — across keyword sets no spreadsheet could hold.
-
Drafting against the map, never inventing it
Outlines, meta copy and internal-link suggestions are generated from the topical map, then read and corrected. The structure is decided before the model is involved.
-
Chained into agentic workflows
What I am building now: chains that carry one brief from keyword set to cluster to map slot to outline to link suggestions, with a checkpoint after each stage instead of one blind prompt.
What does not get automated.
- The map decides the structure. A model can shorten the research behind a row, not choose the row.
- Nothing publishes unread. Generated copy is corrected against the source and the map before it goes live.
- Client data stays out. Keyword sets, site exports and analytics are only processed where the engagement allows it.
- Every script is documented. If I cannot hand it to someone else with its inputs and expected output, it is not finished.
All six tools run on my own input and print what they changed. None of them writes to a live site without a review step, and the client-facing versions are documented before handover.
Contact
Hiring for someone who automates the repetitive work?
I am open to remote SEO and technical SEO roles where tooling is part of the job. Ask for a walkthrough of any tool on this page and I will show it running.
- [email protected]
- Phone
- +92 322 6189669
- Location
- Multan, Pakistan · Remote
- Status
- Open to remote roles