Tteok vs Tteokbokki vs Dduk — Which Site, Which Cake, Which Search

English search treats tteok, tteokbokki, and dduk as three foods. They are one material in different jobs, plus a spelling fork. This network split the jobs on purpose so Google is not asked to rank three thin clones of the same article. If you want the short map, stay on this page. Then leave.

Tteok (this site) is the everyday cake: garae logs, soup ovals, cafe injeolmi, baekseolgi, small-batch steaming, storage. Head queries we will actually answer: tteokguk, how to buy rice cakes, why tteok is hard, frozen versus fresh. Start at /blog/how-to-make-tteokguk/ or /blog/how-to-buy-garaetteok/.

Tteokbokki is a dish, not a spelling of tteok. Cylinders in a sweet-spicy gochujang sauce, usually with fish cake. Rose, cheese, rabokki, mala, and royal soy live on https://tteokbokki.ai/. The first-time method is https://tteokbokki.ai/blog/how-to-make-tteokbokki/. We do not republish that pot here. An older post on this site that talked about street sauce is noindex and points at the hub.

Dduk is another romanization of the same Korean word. This network uses dduk.ai for heritage, ritual, wedding towers, and “how is this different from mochi.” Songpyeon versus mochi: https://dduk.ai/blog/songpyeon-vs-mochi/. If your query is Chuseok pine-scented half-moons or a doljanchi tower, that is their job. If your query is a Tuesday tteokguk, stay here.

Bokki.ai is a third fork: fried-rice and fusion “bokki” names, not classic street tteokbokki. Do not cook a first red pot there. Do not cook tteokguk there.

Spelling you will see in the wild: tteok, dduk, duk, tteok-bokki, topokki, ddeokbokki. They are not different sauces. They are keyboard choices. We keep one canonical URL per job and cross-link instead of cloning.

Cannibalization is the failure mode. Three sites publishing “how to make tteokbokki” would split clicks and look like a doorway network. One site publishing a thin five-paragraph clone of another’s post is why Google crawls and then declines to index. This page exists so authors and crawlers see the split in writing.

What we will not do. We will not put a gochujang ratio on tteok.ai. We will not put a Seollal broth on tteokbokki.ai except as a “wrong pot” pointer. We will not put a wheat-versus-rice braise essay on dduk.ai. Cross-links are enough.

If you arrived from a sister site, you were sent here for soup, storage, or shop cakes. If that is not what you wanted, use the links above. If it is, cook /recipes/tteokguk-seollal-soup/ and read /blog/frozen-vs-fresh-tteok-storage/ before you blame the brand on the bag.

Cafe confusion. “Tteok” on a dessert menu might be injeolmi toast, rice-cake cookies, or a mochi-adjacent ice cream sandwich. Those are this site’s fusion and cafe notes, not dduk’s ritual pages and not tteokbokki’s street pot. When a cafe says “ mochi” on a Korean rice cake, the comparison essay is still on dduk.ai because that is the question people type.

Search intent, bluntly. “tteokbokki recipe” → tteokbokki.ai. “tteokguk” / “korean rice cake soup” → here. “songpyeon” / “tteok vs mochi” → dduk.ai. “how to store rice cakes” → here, with a handoff to dduk for sweet cakes. “garaetteok” → here for buying, tteokbokki.ai for the braise chew.

We are not asking you to remember Hangul. We are asking crawlers not to treat three domains as one article with a different H1. The cakes are the same starch. The dinners are not.