Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Birdy's avatar

New to Laravel: Make View or Return View for dynamic cotent and best seo results..

Hi All, I hope i have posted under the right topic as i am new to laracasts and also laravel within its self.

Im currently building my first laravel application, The current question that is within the back of my head is what would be the best practise for seo results (I hope it makes sense to people reading this!).

If you take freelancer.com for example, When ever someone on there posts a project they need completing along with freelancer profiles, They are instantly submitted to search engines for indexing.

To be able to follow suit here and have my application achieve indexing on both projects posted and members profiles, How would you have laravel render the pages?

Would you use a return view function and literally insert the data into the view from the database, Or does the make view function create a static page specifically for that content and then uses the database to keep the dynamic content up to date?

I hope this has not left people reading bamboozled and thinking what on earth am i talking about, As a newbie to laravel i am somewhat out of my league and unsure to what terms i should be referring to.

I look forward to your input, I hope i can get some insights on what the best approach would be.

Thanks

0 likes
5 replies
ndberg's avatar

I don't really get your question. What do you want to say with that?

Would you use a return view function and literally insert the data into the view from the database, Or does the make view function create a static page specifically for that content and then uses the database to keep the dynamic content up to date?

but: Google doesn't care how you do the things on the server side, what they care about is the result you present.. (except some things like speed, https, etc.)

Birdy's avatar

Basically i mean say for example my web application contains the following pages:

index.blade.php <-- Homepage my-account.blade.php <-- My Account page to edit my profile and view other account related info profile.blade.php <-- Users Profile page just like: @Birdy" target="_blank">https://laracasts.com/@Birdy projects.blade.php <-- The Project i have posted for a freelancer to bid on. freelancers.blade.php <-- This will be a list of all the freelancers usernames where the database will loop through and display like to following example

  1. Birdy
  2. Lara
  3. Steve
  4. Dan
  5. James and so on... (These will href through to the users profile id where when a user visits the users profile for example @Birdy" target="_blank">https://laracasts.com/@Birdy it will render that specfic users details on the profile.blade.php page)

So my question is, Will this be automatically indexable to search engines so for example will my profile (@Birdy)" target="_blank">https://laracasts.com/@Birdy) and every other users profile be indexed when using 1 page known as: profile.blade.php and rendering it with dynamic content as apose to a specfic page like: birdy.blade.php and have the page pull the content from the database.

Here is a freelancer.com example:

A project posted a while back on freelancer.com and is in the index:

Do some Excel Work | Data Entry | Data Processing | Excel www.freelancer.com › Jobs › Data Entry 'Do some Excel Work' job on Freelancer. Work on this job or post your own for free!


And Another example:

Get Traffic to my Website - Freelancer www.freelancer.com › Jobs › Internet Marketing 'Get Traffic to my Website ' job on Freelancer. Work on this job or post your own for free!


So what im getting at is, Will freelancer.com or any similar website use the make view function when posting a job or will they have just one page like i mention above and render that page with specfic database content and just return the view.

Or would you open up your views/projects folder and see that there is not just one view named: projects.blade.php but loads of them going like once they have been posted / created.

project1.blade.php project2.blade.php project3.blade.php project4.blade.php project5.blade.php

Does this make it more confusing or have i managed to get accross what it is i mean? Thanks for taking the time out to comment i appreciate it.

Hopefully i can get accross what it is i mean!

Thanks

ChristopherSFSD's avatar
Level 4

Just do view make and fill it in with the data from the database. The web crawler sees a unique URL for each resource, so you'll be fine. No need to make it complicated or get tricky.

1 like
Snapey's avatar

The search engine crawler does not 'look in folders'. it only sees the pages you explicitly link to somewhere in your site. So, you need an index page that lists all contributors with a link to their page, or you need to dynamically maintain an XML site map.

1 like
thomaskim's avatar

return View::make('... and return view('... are basically the same exact thing. It makes no difference.

Also, like @andi said, what you do on the server side (PHP) makes no difference to Google because they have no idea what you do on the server side. All they care about is the client side, and as long as you didn't deny access or told the bots not to index it or something, it doesn't matter.

Regarding static pages and dynamic pages, what Google and other bots see are just pages. Nothing else. "Dynamic" simply means that the content of the pages change, and this is the case for something like blogs. A contact page rarely ever changes, but they are still both web pages. But Google does not care how the pages are created. They just see a page. That's it.

1 like

Please or to participate in this conversation.