Frequently Asked Questions (FAQ)

Common questions about inblog including content migration, IP tracking exclusion, and pricing details.

Yes, individual creators, freelancers, and sole proprietors can use inblog.

Free Plan: Suited for individual creators with no subscription cost.
Team Plan: The blog setup flow includes a business information step, but you can enter a personal brand name or your own name instead of a company name.

That said, inblog's core features — custom domain, lead capture forms, and SEO analytics — are optimized for business inbound content marketing. There is no separate pricing tier or feature set designed specifically for personal blogging.

Getting started with inblog

The sign-in screen offers two separate sign-in methods, and they use different credentials:

The Sign in with Google button at the top
The email and password fields below the divider

If you signed up with Google, your inblog account has no password of its own. Typing your Google password into the email and password fields returns Invalid login credentials. Use the Sign in with Google button at the top and pick that Google account instead.

Changing your Google password does not change your inblog account. As long as Google authenticates you with the new password, you land in the same inblog account.
If you don't remember how you signed up, try Sign in with Google first.
If you signed up with an email and password, sign-in only completes after you open the link in the confirmation email. Check your inbox and spam folder.
If you signed up with Google but would rather use the email form, use Forgot your password? on the sign-in screen to set a password. After that, email and password sign-in works too.

Sharing one account between several people makes it impossible to tell who did what. If more than one person needs access, have each person sign up with their own account and invite them as team members.

I signed up but never received the confirmation email

If it isn't in your inbox or your spam and promotions folders, it's usually one of these two:

That email address is already registered through Google. Signing up with Google completes verification on the spot, so no confirmation email is sent — and signing up again with the same address usually won't produce one either. Use the Sign in with Google button on the sign-in screen instead; it takes you into the same account you already have.
A typo in the email address. Something like .coom instead of .com means the email is sent but never reaches you. Double-check the address and try again.

If neither applies, send us the email address you signed up with via chat and we'll check the account status.

I already have a free blog (Naver Blog, Tistory, Blogger, WordPress.com, etc.). Why should I use inblog?

Free blogging services give you a place to publish, but inblog is built for business inbound content marketing. The main differences:

Technical SEO handled for you: clean server-rendered HTML, automatic H1–H3 markup, an auto-generated sitemap and robots.txt, and BlogPosting JSON-LD structured data are all applied with no setup.
SEO equity accrues to your own domain: connect a custom domain and your search rankings, backlinks, and domain authority build on your brand's domain instead of a shared free platform.
Turn visitors into leads: built-in lead capture forms plus real-time traffic and keyword analytics let you measure and improve marketing performance, not just publish posts.
Run it without developers: most of the above is configured from the dashboard with no code.

In short, a free blog is mostly "a place to write," while inblog is "a business blog tool that connects search and AI visibility to lead generation."

See inblog pricing

I'm currently running a blog on WordPress / Ghost. Can I migrate my content to inblog?

Yes! inblog provides "content migration support for platforms like WordPress, Ghost, Naver Blog, and more." Notable companies such as Classum and HappyTalk have completed successful migrations to the platform.

How does inblog help my content show up in AI search (GEO), like ChatGPT, Perplexity, or Google AI Overviews?

Getting cited in AI search works much like traditional SEO: AI models crawl and read web content, then quote it in their answers. The keys are a machine-readable structure and clear, quotable content.

What inblog handles automatically:

JSON-LD structured data plus meta and OG tags, so AI crawlers understand each post's topic and structure
Automatic H1–H3 markup and SSR rendering, delivering clean HTML that LLMs can ingest directly
Auto-generated sitemap and robots.txt, so search engines and AI crawlers discover new posts quickly

What you should focus on:

Answer questions directly and up front (FAQ and How-to formats). AI tends to quote paragraphs that state a clear answer.
Include original data, examples, and quotable statistics to raise the odds of being cited.
Build topical authority by covering one subject in depth across related posts.

Like regular SEO, AI search visibility needs time to index and accumulate — results typically take several months to appear.

Will my posts show up in a specific AI tool like Gemini or Claude?

Out of the box, inblog does not block any AI tool from reading your content. Published posts are served as plain HTML, and on top of JSON-LD, the sitemap, and robots.txt, every blog gets an auto-generated llms.txt (open the dashboard Settings screen and use View file under LLMs.txt to see it). The technical groundwork for an AI tool to read and cite your posts is in place.

That said, we can't guarantee that any particular platform will surface or cite your posts. What each AI platform crawls and how it cites sources differ, and so does the outcome depending on your topic and content quality.

A realistic expectation:

Visits arriving through AI search are still small compared with traditional search such as Google. AI answers are often read in place without anyone clicking through.
So it's more realistic to treat AI visibility as a medium-to-long-term channel — the value is in accumulating content that both search engines and AI tools can read — rather than as a source of traffic today.
If Naver search traffic also matters to you, we recommend running your Naver blog alongside inblog rather than replacing it outright.

Moving from a platform that restricts external crawling changes the starting point: your content becomes readable to AI tools in the first place. To improve the odds of being cited from there, see the AI search (GEO) answer above.

My posts are indexed but aren't getting any search traffic or rankings. What should I check?

If Google has indexed your pages but they still aren't showing up in search, it's usually a combination of these three factors:

Duplicate content — If a nearly identical post also lives on another platform (Medium, another blog, etc.), Google typically shows only one version (usually whichever was indexed first or sits on a higher-authority domain) and drops the rest from results. Write your blog posts with a different angle, structure, and wording from your other channels.
Using the default domain — A custom domain ranks far better than the default domain (inblog.io). Connecting your own domain lets search rankings, backlinks, and domain authority accrue to your brand.
Blog age — A new domain or blog usually needs 1–3 months for Google to build trust. Pages can be indexed well before rankings and impressions catch up.

So if indexing is fine, this is usually a matter of time and differentiation, not a bug. Connect a custom domain, differentiate your content, and publish consistently — visibility grows over time.

Can I exclude traffic from specific IPs to avoid skewed page view data?

The platform does not currently offer IP-based tracking exclusion. However, any blog access using the parameter ?traffic_type=internal gets "automatically excluded from page view tracking in the inblog dashboard."

I keep seeing an "internal traffic excluded" notice on my blog. Is something broken?

No — this is expected. When you open your blog from the dashboard using View blog or View post, ?traffic_type=internal is appended to the URL automatically, and the notice simply tells you that this visit is an admin/internal check and is not counted in your stats.

Regular visitors never see it. Readers arriving at the plain URL see no notice, and their visits are counted normally.
Once a tab has been marked as internal, removing ?traffic_type=internal from the URL in that same tab will not hide the notice, and those visits stay excluded — the internal flag is remembered per tab.
To view your blog exactly as a reader does, open the plain URL in a new tab or a private/incognito window.
Keep in mind that visits made that way are counted in your stats, so use the dashboard links for day-to-day checks if you want clean numbers.

My Google Analytics numbers don't match inblog's visit count. Why?

The two are measured differently, so they will not always show the same number. The two most common causes:

Internal traffic handling: visits you open from the dashboard via View blog are excluded from inblog's stats, but Google Analytics still counts them as users. The more often you check your own blog, the higher GA will read.
Different metrics: GA's Total users and inblog's Visits do not count the same unit.

Breaking GA down by source shows how much of the gap comes from dashboard-originated visits (inblog.ai / referral).

I saved my Measurement ID, but the page shows inblog's Measurement ID. Is my GA blocked?

This is expected, and it does not block collection on the Measurement ID you saved. On an inblog blog, inblog's own Measurement ID and yours run together.

The tag script (gtag.js) is loaded once using inblog's Measurement ID, and yours is added on top of it as a config call. That is why checking the network tab in developer tools for googletagmanager.com/gtag/js?id=... only shows inblog's ID.
To confirm your Measurement ID is really firing, check with Google Tag Assistant or the GA realtime report instead.
For page speed, your config call runs 2–3 seconds after the page renders, once the browser is idle. Checking the instant the page opens may be too early.
The two run together on content pages such as posts and listings. Standalone form pages do not apply your Measurement ID.

If data still isn't collected, the Measurement ID itself is usually invalid — an ID from a data stream you no longer use, or a typo. Google's tag server can't resolve it, so nothing is collected.

In Google Analytics, go to Admin → Data streams → Web → your web data stream, copy the Measurement ID again (it starts with G-), and save it in inblog under Settings → Google Analytics → Measurement ID. (Connecting a Measurement ID requires the Team plan or above.)
After saving, it shows up in the GA realtime report within a few minutes. Standard reports take longer to process, so check realtime right after saving.

My blog's total visits don't add up to the per-post view counts. Which one is right?

Both are correct — they count different things, so they are not meant to match.

Total visits counts page views across the whole blog, including the blog home, category, and author pages. The per-post number (shown as Visits in the dashboard) counts only that single post. Adding up your post numbers will therefore never equal the blog total.
Neither number is a unique-visitor count. Both are page-view based, so the same reader opening the same post again is counted again.
Both follow the date range selected at the top of the dashboard (last 28 days by default). Per-post numbers are not all-time figures.

The same date range shows a slightly different total each time I refresh. Why?

Recent days are still being finalized.

Blog total visits are read directly from live traffic records for the most recent few days (roughly today plus the previous two, in your blog's timezone), and from pre-aggregated data for older dates. Recent days keep accumulating visits, and numbers can be adjusted as a day crosses over into the finalized aggregate.
Per-post numbers always come from live records regardless of the date, so any increase you see there is simply newly arrived traffic.
If figures for dates more than a few days old keep changing significantly, send us the date range and the screen you were viewing and we will look into it.

How is inblog priced?

The service "starts at $39/month and scales based on your monthly page views."

I run several blogs. How do I tell which blog a given subscription belongs to?

Subscriptions and billing are managed per blog. Even when one account owns several blogs, there is no combined screen that lists every subscription in one place, so you check each blog in turn.

Where to look: pick the blog in the dashboard, then open Subscription in the left menu. (This menu is only visible to blog owners and admins.)
To find a blog by payment date: the same screen has an Invoices section listing the billing date and invoice for each payment. The blog holding an invoice dated the day you're looking for is the one that subscription belongs to.
For a subscription you have since cancelled or replaced, the Billing history section below it shows each subscription's start and end date.
For the subscription currently in use, the top of the screen also shows the plan and the renewal date. (If cancellation is scheduled you'll see an end date instead, and admin-granted or bulk-billed plans may show no date at all.)
My Page (the profile menu at the top right) only holds profile and security settings, so no subscription details appear there.

If you have too many blogs to compare, contact us in chat with the account email used for payment and the date the subscription started.

Which plan do I need to use the REST API or CLI?

The REST API and @inblog/cli are available on any paid plan (Team Plan and above).

There is no difference in API features between plan tiers — you can work with the same resources (posts, tags, authors, blogs, redirects, forms, lead responses).
Billing scales with your traffic (page views), not with the plan tier.
Generate an API key under Dashboard → Settings → API Keys, and use @inblog/cli for terminal and automation work. See inblog CLI and AI Skills and the API docs for details.
The REST API and CLI also work during the 14-day free trial. Once the trial ends and your blog moves to the Free Plan, existing API keys stay visible but API calls no longer work.

My API key is issued on the Free Plan, but calls fail (n8n, Make, etc.)

On the Free Plan you can still open the API key screen and see or create a key, but actual API calls only work on a paid plan (or during the free trial). So if you connect a Free Plan key to a workflow tool like n8n or Make, the key looks valid but requests fail with an auth/permission error.

During the free trial: API access works.
After moving to the Free Plan: keys exist but cannot be used — resubscribe to Team Plan or above to resume calls.

Can I make an individual post private?

inblog does not currently offer a way to make a single post private — once published, a post is served at a public URL that anyone can open.

To show a post to specific people before publishing, share the editor's preview link. The preview path is different from the live post URL, so it is not counted in your page view or visit analytics.

inblog does not offer a paid membership (gated access) feature for restricting content to subscribers.

If I downgrade to the Free Plan, what happens to my connected custom domain?

Custom domain connection is a paid feature, so when you cancel a paid subscription your blog moves to the Free Plan and the connected custom domain (e.g. example.com/blog or blog.example.com) is disconnected.

While the domain is disconnected, URLs that search engines had indexed under that custom domain return 404. (The blog and its posts stay public on inblog's default address.)
If you resubscribe to a paid plan, you can reconnect the same custom domain and restore those URLs.
Because frequently changing domains can hurt your SEO, we recommend keeping the same domain whenever possible.

Can I pause my subscription for a month or two and resume later?

There is no separate pause subscription feature. Instead, cancel to move to the Free Plan, then start a paid subscription again whenever you need it.

Once you schedule a cancellation, paid features stay active until the end of the current billing cycle.
While you are away, your blog and published posts are not deleted — they stay public on inblog's default address (*.inblog.io), and you can still publish new posts.
During the Free Plan period the custom domain is disconnected and those URLs return 404, so review the custom domain question above if search traffic matters to you.
You can cancel from Subscription & Billing → Manage subscription in the dashboard.

Which currency am I billed in, and can I get a local-currency invoice?

inblog subscriptions are sold and processed by Paddle, our Merchant of Record, and charged in USD — inblog does not process the payment directly in your local currency.

The invoice issued after payment comes from Paddle's UK entity in USD, and that document is the official record of the transaction.
You can find it under Subscription & Billing → Invoices, or in the email you receive at checkout.
If you need documentation of the amount actually charged in your local currency, use the foreign-transaction record or local-currency statement from your card issuer — it shows the converted amount your bank billed you at the exchange rate on the approval date.

How do I change the email that receives payment receipts, and can I get past receipts resent?

Receipts (invoices) go to the email registered at checkout. The email shown at the top of the Subscription screen is the account email that started the payment, so it may differ from the address actually receiving your receipts.

If you just need a past receipt, you don't have to wait for a resend. The Invoices section on the same screen lists the billing date and amount for each payment, and for payments with an issued invoice the download icon at the right of the row opens the PDF straight away. (Subscription only appears in the left menu for blog owners and admins.)
To change the recipient address itself, contact us in chat. There is no screen for editing it yourself yet — My Page only covers your name, avatar, language, password, and multi-factor authentication, and holds nothing billing-related.
Include your blog address, the email currently receiving receipts, and the new email and we'll take care of it.
If the person in charge has changed and you also need the login account email updated, use the same route. The receipt address and the login account email are managed separately, so let us know which one you want changed.

I updated my payment card, but the old card's charge is still listed. Was I billed twice?

No. What you see is the record of a past payment that was already authorized and captured — it is not a duplicate charge.

Changing your payment method only changes the card used for future renewals. It does not automatically cancel a completed payment or move it onto the new card.

To change the card: Subscription → Payment method → Change card. This opens the payment provider's payment-method screen, and the new card applies from the next payment onward. (Subscription only appears in the left menu for blog owners and admins — if you can't see the menu at all, ask the blog owner for admin access, then refresh the page.)
You don't have to delete the old card first. Saving a new card replaces the payment method, and you can remove the previous card afterwards from the Saved cards list.
If you need the earlier charge refunded and re-billed to the new card, changing the card does not do that. A refund and a new payment are two separate actions, so contact us in chat.
Once a refund is approved, it can take about 7 business days to appear from your card issuer.
To speed things up, include your blog address, the last 4 digits of the old and new cards, and what you want done (refund only, or refund then re-bill). Please don't send full card numbers.

Some posts look different from what I wrote, or certain words appear changed.

This is almost always caused by your browser's automatic translation. When your browser's language (e.g. English) differs from the page's language (e.g. Korean), Chrome, Edge, and similar browsers may auto-translate the page and swap words in the process, so the text looks altered. (For example, "형사" showing up as "형사팀".)

In this case the published content itself is fine — it only looks different in the viewer's browser.
Because translation results differ by browser and device, this often shows up as "it looks wrong on one computer but normal on another."

How to fix:

Click the translate icon in the address bar and choose to show the original language.
In Chrome, right-click the page and select "Never translate this page."
If it persists, turn off automatic translation for the site in your browser settings.

I changed my author name, but the author page URL (`/author/...`) still shows the old one.

The slug in an author page URL is set when the account is created and is managed separately from the author name, so renaming the author leaves the URL string untouched.

The display name and page title on the public author page do reflect the new name. Only the address string keeps the old one.
Neither the dashboard nor the REST API/CLI currently offers a way to change the slug directly. The editable fields on the API and CLI are the author name (author_name) and profile image (avatar_url).
Don't delete and re-create the author to work around this. It can detach the author from posts that already reference them, and it isn't a supported way to mint a new slug.

If having a particular name in the URL is a real problem for you, send us the blog address and the author page address over chat. Changing the address means also setting up a permanent redirect so existing search traffic isn't lost, so we handle these case by case.

On the Team Plan you can insert global script tags (Google Tag, Google Ads, etc.) from Settings → global script injection. For AdSense specifically, note these conditions and limits:

It works only on a paid blog with a connected custom domain. You can't run AdSense while using only the default domain (inblog.io).
Only AdSense Auto ads (via code injection) are supported.
Uploading an ads.txt file and placing ads manually inside the post body (inserting ad slots at chosen positions) are not currently supported.

Keep in mind you'd still be paying the monthly subscription, and AdSense alone may not cover that cost. Affiliate marketing links can be an alternative way to earn revenue.

Can I download or export my dashboard data (visitors, traffic)?

Analytics data such as visitors and traffic cannot be downloaded or exported — it is available for viewing in the dashboard only.

These data sets can be exported:

Post list: use the Download CSV button at the top right of the post manager (adjust the fields with Customize Columns).
Leads (form responses): on the leads screen, select View all leads to export an Excel workbook with one worksheet per form, or select one form to export a CSV.
Posts and leads: also retrievable through the REST API (available on the Team Plan and above).

If you plan to pause or cancel your subscription, export anything you need to keep before you cancel.

Last updated 2026-08-06

PreviousPricing