If you came here to build a custom GPT for your blog, the plan has to change. At the time of writing (October 2026), OpenAI no longer lets personal ChatGPT accounts create new GPTs. That covers Free, Go, Plus and Pro. It has also announced that custom GPTs will be retired on December 11, 2026.
The useful part of a custom GPT is still easy to get: a chat assistant that starts every conversation with your instructions and your reference files. ChatGPT Projects, Claude Projects and Gemini Gems all work that way, and each can be tried without paying.
Below: what changed, which tool fits which job, two setups worth building, instructions you can copy, and the limits to know before you share anything.
What happened to custom GPTs
OpenAI's help pages now say new GPT creation and publishing aren't available on personal accounts. Business, Enterprise and Edu workspaces can still build them, but only until October 26, 2026, and every custom GPT stops working on December 11 (a few Enterprise workspaces can get an extension into February 2027). The dates are in OpenAI's custom GPT retirement and migration FAQ, which is worth reading directly because the rollout is still moving.
The replacement is called Plugins. A plugin bundles "skills" (reusable instructions), reference files and connected apps.
If you already own a GPT, OpenAI says migrating it turns your instructions into a skill and copies your knowledge files across as reference files. Two things don't come along. Custom Actions, the feature that let a GPT call an outside API, have to be rebuilt. And the migrated plugin starts private, so people using your old shared link lose access until you share it again. Migration is being switched on for different accounts at different times, so watch for the migration prompt in your account and act on it before the deadline.
I wouldn't build anything new for a solo blog on plugins yet. The sharing documentation is written for company workspaces, and it doesn't clearly say what a personal account can share with outsiders. Check what your own account offers before you plan around it.
Instructions, knowledge files and sharing
Whatever the product calls them, these assistants have the same three parts.
| Part | What it does |
|---|---|
| Instructions | Standing rules: role, tone, what to avoid, what to do when unsure |
| Knowledge files | Documents the assistant can look things up in |
| Sharing | Who else can open and use it |
Keep rules in the instructions and reference material in the files. A style rule buried on page nine of an uploaded PDF may only be seen when the assistant happens to pull up that passage, so put rules in the instructions. OpenAI's own guidance says the same, and adds that plain, text-heavy files work better than heavily designed ones.
Nothing here retrains the model. Uploading past articles gives the assistant examples to look at, and it'll imitate them roughly. That's less than the "trained on your voice" claim you'll see elsewhere.
Which tool to use
| Tool | Sharing with other people |
|---|---|
| ChatGPT Projects | Invite people, or "Anyone with a link"; personal plans cap collaborators |
| Claude Projects | Team and Enterprise plans only |
| Gemini Gems | Specific people, anyone with the link, or public |
ChatGPT Projects are on every plan including Free, though the free plan allows only five files per project at the time of writing. Claude Projects are also on the free plan, with a limit of five projects. Gems are made in the Gemini web app and don't need a paid subscription.
For a private writing assistant, use whichever chatbot you already write with. For something readers can open, a Gem is the only one of the three built to be handed to strangers.
Setup 1: a private writing assistant
This is the one I'd build first. It drafts outlines in your structure and flags places where a draft drifts from your style. It doesn't write the post.
- Write a one-page style guide: who you write for, your tone, formatting habits, phrases you never use.
- Pick three to five published articles that sound most like you and save each as plain text or Markdown.
- Create a project (or Gem), paste the instructions below, and upload the style guide and articles.
- Test it on a post you've already published. Ask for an outline on that topic and compare it with what you actually wrote, then tighten the instructions where it missed.
Copy this and fill in the brackets:
You are an editing and outlining assistant for [blog name], a blog about [topic] written for [reader, e.g. people starting their first affiliate site].
The uploaded style guide is the rulebook. The uploaded articles are examples of the voice. When they conflict, follow the style guide.
When I ask for an outline, give me a working title, the one question the post answers, and five to eight headings with a one-line note under each. Before you write it, ask me what I know first-hand about the topic.
When I paste a draft, don't rewrite it. List each place it breaks the style guide, quote the sentence, and suggest one fix.
Never invent statistics, prices, quotes, sources or personal experiences. If a claim needs a source, write [NEEDS SOURCE] so I can check it myself.
Don't use these words or phrases: [your banned list].
If you're unsure what I want, ask one question before you start.
The outline step pairs well with a repeatable drafting routine. If you don't have one, this process for writing posts faster without making them worse covers the parts the assistant can't do for you.
