Must be about Laravel: We understand the Laravel ecosystem can be vast, but posts that are **not** directly related to Laravel should be posted elsewhere. Additionally, content regarding framework comparison is not allowed on /r/Laravel.
[>]
Be Civil: Toxicity doesn't ship in /r/Laravel Name-calling, insults, unnecessary profanity, or personal attacks of any kind will **not** be tolerated. We take pride in providing a supportive space for our community. Let's work together to create a positive and welcoming environment for everyone.
[>]
Don't Spam / No Clickbait: Spam, low effort, or obvious AI generated content will be removed based on community reports, votes, and comments. Self-promotion is fine if it's valuable- don't post back-to-back or drop links without engaging. "What is Laravel" posts or near copy-paste from docs aren't resourceful. Clickbait or poorly titled posts aren't allowed- titles should clearly convey the topic. No hijacking threads to promote your own product. Keep discussions focused and relevant
[>]
No Help/Support Posts: /r/Laravel is not an individual support subreddit - it's a space for discussions, resources, and news related to the Laravel ecosystem vs. posts on issues specific to the OP. If you need help, we have some resources -- you can ask in our weekly help thread, stickied at the top of the subreddit, ask in the official Laravel Discord, or ask over at /r/PHPHelp.
[>]
No "Help Wanted" or "Available for Hire" posts: This prevents spam, protects the community, encourages on-topic discussion, and guides users to more suitable platforms for their job-related inquiries. Visit the official Laravel job board, LaraJobs, to advertise or apply for open positions: https://larajobs.com
Works well
A package or tool you built that solves a specific Laravel problem, with a clear title and real engagement in the comments.
A tutorial or technique write-up that teaches Laravel developers something they can use in their own code.
A short case study of how you solved a real problem in a Laravel project, written as a discussion rather than a pitch.
A question or discussion about Laravel ecosystem practices, like deployment patterns or package choices, that invites other developers to share their approach.
News about a Laravel ecosystem release or update, with your own take on what it means for people building with the framework.
Avoid
Posting anything that is not directly about Laravel, since off-topic posts get removed under “Must be about Laravel”.
Writing framework comparison posts, like Laravel versus another framework, because the rules call that content out by name.
Dropping your link and leaving, since the spam rule says self-promotion is fine only if you engage in the thread.
Posting the same promotional thing repeatedly or back-to-back, which the “Don't Spam / No Clickbait” rule singles out.
Using a vague or clickbait title, because titles must clearly convey the topic.
Publishing obvious AI generated content or near copy-paste from the docs, both of which are named as removable under the spam rule and the AI content policy is listed as discouraged in our brief for this community, so treat AI drafted posts as a real removal risk here and write in your own words with your own experience in them.
What r/laravel Is For
This is the community for Laravel, a free and open-source PHP web framework. The description says the framework is known for expressive, elegant syntax that frees you to create without sweating the small things. The people here are Laravel developers and people building with Laravel, and the rules say the space is for discussions, resources, and news related to the Laravel ecosystem. It is not a support desk for individual problems, and it is not a job board. If your product, tutorial, or story connects directly to building with Laravel, this is your room. If it is about some other framework or a general business topic with no Laravel angle, the first rule says to post it somewhere else.
Rules That Matter Before Posting
The rule that decides most marketing outcomes here is “Don't Spam / No Clickbait”. It says self-promotion is fine if it is valuable, but you cannot post back-to-back, cannot drop links without engaging, and cannot hijack threads to promote your own product. Titles must clearly convey the topic, so a vague or clickbait headline gets your post removed before anyone reads it. “Must be about Laravel” is the other gate, because anything not directly related to Laravel belongs elsewhere, and framework comparison posts are not allowed at all. “Be Civil” matters if you end up in a heated comment thread, since name-calling, insults, and personal attacks are not tolerated. “No Help/Support Posts” matters if your plan is to post a question about your own project, because that belongs in the weekly help thread instead. “No 'Help Wanted' or 'Available for Hire' posts” matters if you are recruiting, because job posts go to LaraJobs, not here.
What To Post
A good post here is directly about Laravel and gives something the community can use. Think a package you built that solves a real Laravel problem, a tutorial that teaches a technique, a write-up of how you solved something in a Laravel codebase, or news about the ecosystem. If you are promoting your own tool, the rule says self-promotion is fine if it is valuable, so lead with the value and stay in the thread answering questions. Write a title that clearly says what the post is about, because vague or clickbait titles are not allowed. Do not post a support question about your own app as a main post, use the weekly help thread for that.
What To Avoid
The fastest way to get removed is posting something that is not directly about Laravel, or a framework comparison, under “Must be about Laravel”. Dropping a link with no engagement, posting back-to-back promotions, or hijacking someone else's thread to pitch your product all trip “Don't Spam / No Clickbait”. A clickbait or unclear title gets removed too. Help and support posts about your own specific issue are removed under “No Help/Support Posts”, and the same rule points you to the weekly help thread, the official Laravel Discord, or /r/PHPHelp. Job listings and hire-me posts are removed under “No 'Help Wanted' or 'Available for Hire' posts”, which sends you to LaraJobs. Name-calling, insults, unnecessary profanity, or personal attacks break “Be Civil”. Low effort posts, obvious AI generated content, and near copy-paste from the docs are also named as removable.
Use Rankhog before posting in r/laravel
Want the version that does not run out? Subscribers get unlimited tool runs and more careful checks before posting.
Start your 3-day free trial. Card required. $99/month after trial. Next, connect a verified Reddit account; no strategy starts until you explicitly start Rankhog.
Yes, conditionally. The “Don't Spam / No Clickbait” rule says self-promotion is fine if it is valuable, but you cannot post back-to-back, cannot drop links without engaging, and cannot hijack threads to promote your own product.
Can I post about my SaaS if it is not built with Laravel?
Yes, if it is genuinely about the Laravel ecosystem, like a package, a tutorial, or a tool that Laravel developers would use. A general marketing tool with no Laravel angle does not fit.
Can I ask for help debugging my app?
No. “No Help/Support Posts” says the subreddit is not for individual support, and it points you to the weekly help thread, the official Laravel Discord, or /r/PHPHelp instead.
Can I post a job listing or say I am looking for work?
No. “No 'Help Wanted' or 'Available for Hire' posts” bans job posts and points you to LaraJobs, the official Laravel job board.
Can I post a comparison of Laravel against another framework?
No. “Must be about Laravel” says framework comparison content is not allowed on the subreddit.