SEO Practical
Building trust before you have any testimonials
One testimonial that looks invented takes the honest claims on the page down with it. There are other kinds of evidence available while you have none.
Technote
15 articles· SEO · Founders
SEO Practical
One testimonial that looks invented takes the honest claims on the page down with it. There are other kinds of evidence available while you have none.
SEO Practical
The about page looks like a formality, yet it is the page people reopen just before enquiring or paying. What they are checking is not your company timeline.
SEO Practical
An article sitting on page two has already done half the work. Fixing it usually reaches the front page for far less time than writing something new.
SEO Practical
Business details, a refund policy and a published process build trust. Invented testimonials, once spotted, take everything else down with them.
SEO Practical
You do not need to read every analytics screen. Three numbers tell you which article to fix and which kind to write more of.
SEO Practical
A site the search engines do not know about might as well not exist. Registration takes thirty minutes, and there are specific screens to check afterwards.
SEO Practical
Hide the price and you become a "call us" service; list only inclusions and you inherit a scope dispute. One page structure removes both problems at once.
SEO Practical
You do not need many pages. Five is enough — as long as each one has a decided question it answers for the visitor.
SEO Practical
The same ten posts become a different site once they point at each other. Links are the reader's next step and, to a search engine, your explanation of…
SEO Intro
Articles usually fail on sequence, not on prose. Keep four parts in the right order and readers finish, no writing course required.
SEO Intro
Every field is a question. Ask too many of someone who has not decided to trust you yet and you get a closed tab instead of an answer.
SEO Intro
Ten articles written in no particular order stay ten separate articles. Fix the ratio and the sequence of broad and narrow pieces and the same effort builds something…
Cited
Topics outside WordPress are collected on Dongji Communication Tech Insights, run by the same team. The summaries below are quoted from the originals; the titles link to them.
Working with AI
Writing a CLAUDE.md — teaching an AI coding assistant your project
AI coding tools such as Claude Code, Cursor and Copilot do better work the more precisely they know your project. Here is a structure and a set of principles that hold up.
Working with AI
Prompting an AI for UI design — drafting with Claude and GPT
Asking an AI to "make a nice button" gets you a disappointing button. Structured prompts that carry constraints, references and a defined role get you the design you meant.
Themes & plugins
SCSS from the ground up — variables through module structure
The core syntax of SCSS (Sass) and what it solves that plain CSS cannot: variables, nesting, mixins, @use and module structure — organised around patterns you can use immediately.
Themes & plugins
Design tokens and theme colour systems — brand identity in SCSS variables
How to turn a colour palette from a pile of hex codes into a system that means something — semantic token structure and SCSS variable patterns, from a real project.
Performance optimization
Designing a responsive typography system — the science of readability
Hard-coded pixel font sizes are over. Type scales, fluid sizing with clamp(), Korean webfont optimisation and line-height ratios — building typography that reads well on any screen.
Development workflow
From Figma to SCSS — a designer-developer handoff guide
Minimising what gets lost between a Figma file and the code: extracting tokens, naming components, keeping the spacing system in sync — the whole workflow, step by step.